Please type a plus sign (+) inside this box — > | + |
Under the Paperwork Reduction Act of 1 995, no persons are re
PTO/SB/05 (4/98)
Approved for use through 09/30/2000. OMB 0651-0032 ■
Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
a collection of information unless it displays a valid OMB control number
UTILITY
PATENT APPLICATION
TRANSMITTAL
i for new nonprovisional applications under 37 C.F.R, § 1.53(b),
Attorney Docket No. |
First Inventor or Application Identifier] Paul Lapstun
Title | INTERACTIVE PRINTER WITH ACTUATOR
Express Mail Label No. |
Assistant Commissioner for Patents
ADDRESS TO: Box Patent Application
Wflfihinfitnn, l?fi 80831
5. | | Microfiche Computer Program (Appendix)
6. Nucleotide and/or Amino Acid Sequence Submission
(if ap plicabl e, all necessary)
a. | Computer Readable Copy
b. | Paper Copy (identical to computer copy)
c. | Statement verifying identity of above copies
* Fee Transmittal Form (e.g., PTO/SB/17)
| (Submit an original and a duplicate for fee processing)
2. |x I Specification [Total Pages I qq I]
(preferred arrangement set forth below) I 1
- Descriptive title of the Invention
- Cross References to Related Applications
- Statement Regarding Fed sponsored R&D
- Reference to Microfiche Appendix
- Background of the Invention
- Brief Summary of the Invention
- Brief Description of the Drawings (if filed)
- Detailed Description
- Claim(s)
- Abstract of the Disclosure
|X | Drawing(s) (35 U.S.C. 113) [Total Sheets [ 59 | ]
Oath or Declaration [Total Pages [ 3 j ]
a. | X I Newly executed (original or copy)
□
DELETION OF INVENTORY
Signed statement attached deleting
inventor(s) named in the prior application,
see 37 C.F.R. §§ 1.63(d)(2) and 1.33(b).
3: IN ORDER TO BE ENTITLED TO PAY SMALL E>
ACCOMPANYING APPLICATION PARTS
| X | Assignment Papers (cover sheet & document(s))
□ 37 C.F.R.§3.73(b) Statement I 1 Power of
(when there is an assignee) I I Attorney
| | English Translation Document (if applicable)
n Information Disclosure I I Copies of IDS
Statement (IDS)/PTO-1449 I I Citations
| | Preliminary Amendment
□ Return Receipt Postcard (MPEP 503)
(Should be specifically itemized)
IT! ISSLSl 1 Statement filed in prior application,
^ fprSE; 1 — 1 Status stil,pro P erand desired
n Certified Copy of Priority Document(s)
(if foreign priority is claimed)
. j I Other
16. If a CONTINUING APP LICATION, check appropriate box, and supply the requisite information below and in a preliminary ai
| | Continuation Divisional Continuation-in-part (CIP) of prior application No: I
Prior application information- Examiner Group /Art Unit:
For CONTINUATION or DIVISIONAL APPS only : The entire disclosure of the prior application, from which an oath or declaration is supplied
Customer Number or Bar Code Label \ 24011
..(Insert .Customer !^;^A^^bar^co^ m J^^here)\
Correspondence address below
Kia Silverbrook
Silverbrook Research Pty Ltd
393 Darling Street
AUSTRALIA
61-2-9818-6633 I Fax | 61-2-9818-671 f
Name (Print/Type)
Kia Silverbrook^—)
| Registration No. (Attorney/Agent)
Signature
I A A C_ | Dafe
May 16,2000
Burden Hour Statement: This form is estirria'ted to take 0 2 hours to complete Time will vary depending upon the needs of the individual case. Any
comments on the amount of time you are required to complete this form should be sent to the Chief Information Officer, Patent and Trademark Office
Washington, DC 20231 . DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS SEND TO: Assistant Commissioner for Patents
Box Patent Application, Washington, DC 20231.
Under the Paperwork Reduction A
Approved for use through 09/30/2000. OMB 0651-0031
Patent and Trademark Office; U S. DEPARTMENT OF COMMERCE
re required to respond to a collection of information unless it displays a
STATEMENT CLAIMING SMALL ENTITY STATUS
(37 CFR 1.9(f) & 1.27(c))-SMALL BUSINESS CONCERN
Appii^nt Patents. nriftentifisr: Silverbrook Research Pty Ltd
Application or Patent No.:
Filed orlssued: May , 2000
Title: INITFRACTIVF PRINTFR WITH ACTUATOR
I hereby state that I am
ryl the owner of the small business concern identified below:
□ an official of the small business concern empowered to act on behalf of the concern identified below:
NAME OF SMALL BUSINESS CONCERN Silverbrook Research Pty. Ltd.
addrfss of small business concern 393 Darling Street, Balmain, NSW 2041 , Australia
I hereby state that the above identified small business concern qualifies as a small business concern as defined
13 CFR Part 121 for purposes of paying reduced fees to the United States Patent and Trademark Office. Questions relatec
to size standards for a small business concern may be directed to: Small Business Administration, Size Standards Staf
409 Third Street, SW, Washington, DC 20416.
o and remain with the small business c
D2 the specification filed herewith with title as listed above.
□ the application identified above.
□ the patent identified above.
If the rights held by the above identified small business concern are not exclusive, each individual, cone-
organization having rights in the invention must file separate statements as to their status as small entities, and no righ
to the invention are held by any person, other than the inventor, who would not qualify as an independent inventor under
37 CFR 1.9(c) if that person made the invention, or by any concern which would not qualify as a small business
under 37 CFR 1.9(d), or a nonprofit organization under 37 CFR 1.9(e).
Each person, concern, or organization having any rights in the invention is listed below:
Q3 no such person, concern, or organization exists.
□ each such person, concern, or organization is listed below.
ir organization having rights to the
I acknowledge the duty to file, in this application or patent, notification of any change in status resulting in loss c
entitlement to small entity status prior to paying, or at the time of paying, Hie earliest of the issue fee or any maintenanc 3
fee due after the date on which status as a small entity is no longer appropriate. (37 CFR 1 .28(b))
name of person signing Kia Silverbrook
TITLE OF PERSON IF OTHER THAN OWNER
address OF PERSON/-SIGNING 393- $) arling Street, Balmain, NSW 2041 , Australi a
SIGNATURE ( /LAW C_ date May 16, 2000
Burden Hour Statement: This form is estimated to take 0.2 hours to complete. Time will vary depending upon the needs of the individual case.
m """"" k ,ho amount nf « m = ^ u are required to complete this form should be sent to the Chief Information Officer, Patent and Trademark Ol
SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Assistant Commissioner for Patents
- 1 -
INTERACTIVE PRINTER WITH ACTUATOR
FIELD OF INVENTION
The present invention relates to a printer for printing an interface onto an
surface to produce an interface surface.
5 The invention has been developed primarily to allow a user to press a button on
an interactive printer and thereby obtain a predetermined interface surface which allows
interaction with networked information, thereby to enable access to further interactive
printed matter on demand via the printer. Although the invention will largely be
described herein with reference to this use, it will be appreciated that the invention is not
1 0 limited to use in this field.
CO-PENDING APPLICATIONS
Various methods, systems and apparatus relating to the present invention are
disclosed in the following co-pending applications filed by the applicant or assignee of
the present invention simultaneously with the present application:
15 NPA001US, NPA002US, NPA003US, NPA004US, NPA005US, NPA006US,
NPA007US, NPA008US, NPA009US, NPA010US, NPA012US, NPA016US,
NPA017US, NPA018US, NPA019US, NPA020US, NPA021US, NPA030US,
NPA035US, NPA048US, NPA050US, NPA051US, NPA052US, NPA075US,
NPB001US, NPB002US, NPK002US, NPK003US, NPK004US, NPK005US,
20 NPK007US, NPM001US, NPM002US, NPM003US, NPM004US, NPN001US,
NPN002US, NPN003US, NPP001US, NPP002US, NPP003US, NPP005US,
NPP006US, NPP007US, NPP008US, NPP016US, NPP017US, NPP018US,
NPP019US, NPS001US, NPS003US, NPS020US, NPT001US, NPT002US,
NPT003US, NPT004US, NPX001US, NPX003US, NPX008US, NPX011US,
25 NPX014US, NPX016US, NPX020US, NPX022US, IJ52US, IJM52US,
MJ10US, MJ11US, MJ12US, MJ13US, MJ14US, MJ15US, MJ34US, MJ47US,
MJ52US, MJ58US, MJ62US, MJ63US, PAK04US, PAK05US, PAK06US,
PAK07US, PAK08US, PEC01US, PEC02US.
30 The disclosures of these co-pending applications are incorporated herein by cross-
reference. Each application is temporarily identified by its docket number. This will be
replaced by the corresponding USSN when available.
NPP008US
-2-
BACKGROUND
Presently, a user of a computer system typically interacts with the system using
a monitor for displaying information and a keyboard and/or mouse for inputting
information. Whilst such an interface is powerful, it is relatively bulky and non-portable.
5 Information printed on paper can be easier to read and more portable than information
displayed on a computer monitor. However, unlike a keyboard or mouse, a pen on paper
generally lacks the ability to interact with computer software.
SUMMARY OF INVENTION
According to a first aspect of the invention, there is provided a printer for
1 0 printing a first interface onto a first surface, the first interface including first coded data
and being at least partially based on first document data that includes first identity data
indicative of at least one identity, the identity being associated with a region of the first
interface, the printer including:
an actuator;
15 a coded data generator configured to generate the first coded data based at least
partially on the first identity data; and
a printing mechanism;
wherein the printer is configured to print the first interface onto the first surface, using
the printing mechanism, in response to actuation of the actuator.
20 Preferably, the first interface includes visible information in addition to the first
coded data, the visible information being based at least partially on the first document
data.
Preferably, the visible information is indicative, to a user, of one or more
options, the printer being configured to:
25 receive indicating data indicative of secondary document data associated with
at least one of the options, the indicating data being sensed, by a sensing device, from the
first coded data, when one of the options is designated using the sensing device;
generate a second coded data based at least partially on the secondary document
data; and
NPP008US
-3-
print a second interface onto a second surface on the basis of the indicating
data.
In a preferred form, the printer includes an input module configured to:
receive, from the sensing device, the indicating data;
5 generate second indicating data based on the first indicating data, the second
indicating data being at least partially indicative of the response data; and
send the second indicating data to a computer system;
the printer being configured to receive the secondary document data from the
computer system.
10 In a preferred form, the options include any one or more of the following:
printer status;
printer consumables status;
an upper level of a hierarchical help menu;
an upper level of a network document directory; and
15 a document function menu;
According to a second aspect of the invention, there is provided an interface
surface produced by a printer according to the first aspect.
NPP008US
_4-
BRIEF DESCRIPTION OF DRAWINGS
Preferred and other embodiments of the invention will now be described, by
way of non-limiting example only, with reference to the accompanying drawings, in
which:
5 Figure 1 is a schematic of a the relationship between a sample printed netpage and its
online page description;
Figure 2 is a schematic view of a interaction between a netpage pen, a netpage printer, a
netpage page server, and a netpage application server;
Figure 3 illustrates a collection of netpage servers and printers interconnected via a
10 network;
Figure 4 is a schematic view of a high-level structure of a printed netpage and its online
page description;
Figure 5 is a plan view showing a structure of a netpage tag;
Figure 6 is a plan view showing a relationship between a set of the tags shown in Figure
15 5 and a field of view of a netpage sensing device in the form of a netpage pen;
Figure 7 is a flowchart of a tag image processing and decoding algorithm;
Figure 8 is a perspective view of a netpage pen and its associated tag-sensing field-of-
view cone;
Figure 9 is a perspective exploded view of the netpage pen shown in Figure 8;
20 Figure 10 is a schematic block diagram of a pen controller for the netpage pen shown in
Figures 8 and 9;
Figure 1 1 is a perspective view of a wall-mounted netpage printer;
Figure 12 is a section through the length of the netpage printer of Figure 1 1 ;
Figure 12a is an enlarged portion of Figure 12 showing a section of the duplexed print
25 engines and glue wheel assembly;
Figure 13 is a detailed view of the ink cartridge, ink, air and glue paths, and print engines
of the netpage printer of Figures 1 1 and 12;
Figure 14 is a schematic block diagram of a printer controller for the netpage printer
NPP008US
-5-
shown in Figures 1 1 and 12;
Figure 15 is a schematic block diagram of duplexed print engine controllers and
Memjet™ printheads associated with the printer controller shown in Figure 14;
Figure 16 is a schematic block diagram of the print engine controller shown in Figures
5 14 and 15;
Figure 17 is a perspective view of a single Memjet™ printing element, as used in, for
example, the netpage printer of Figures 10 to 12;
Figure 18 is a perspective view of a small part of an array of Memjet™ printing
elements;
1 0 Figure 1 9 is a series of perspective views illustrating the operating cycle of the Memjet™
printing element shown in Figure 13;
Figure 20 is a perspective view of a short segment of a pagewidth Memjet™ printhead;
Figure 21 is a schematic view of a user class diagram;
Figure 22 is a schematic view of a printer class diagram;
1 5 Figure 23 is a schematic view of a pen class diagram;
Figure 24 is a schematic view of an application class diagram;
Figure 25 is a schematic view of a document and page description class diagram;
Figure 26 is a schematic view of a document and page ownership class diagram;
Figure 27 is a schematic view of a terminal element specialization class diagram;
20 Figure 28 is a schematic view of a static element specialization class diagram;
Figure 29 is a schematic view of a hyperlink element class diagram;
Figure 30 is a schematic view of a hyperlink element specialization class diagram;
Figure 3 1 is a schematic view of a hyperlinked group class diagram;
Figure 32 is a schematic view of a form class diagram;
25 Figure 33 is a schematic view of a digital ink class diagram;
Figure 34 is a schematic view of a field element specialization class diagram;
NPP008US
-6-
Figure 35 is a schematic view of a checkbox field class diagram;
Figure 36 is a schematic view of a text field class diagram;
Figure 37 is a schematic view of a signature field class diagram;
Figure 38 is a flowchart of an input processing algorithm;
5 Figure 3 8a is a detailed flowchart of one step of the flowchart of Figure 3 8 ;
Figure 39 is a schematic view of a page server command element class diagram;
Figure 40 is a schematic view of a resource description class diagram;
Figure 41 is a schematic view of a favorites list class diagram;
Figure 42 is a schematic view of a history list class diagram;
1 0 Figure 43 is a schematic view of a subscription delivery protocol;
Figure 44 is a schematic view of a hyperlink request class diagram;
Figure 45 is a schematic view of a hyperlink activation protocol;
Figure 46 is a schematic view of a form submission protocol;
Figure 47 is a schematic view of a commission payment protocol;
1 5 Figure 48 is a flowchart of document processing in a netpage printer;
Figure 49 is a schematic view of a set of radial wedges making up a symbol;
Figure 50 is a schematic view of a ring A and B symbol allocation scheme;
Figure 51 is a schematic view of a first ring C and D symbol allocation scheme;
Figure 52 is a schematic view of a second ring C and D symbol allocation scheme;
20 Figure 53 is a simple exploded view of the wallprinter;
Figure 54 is an exploded view of the ink cartridge;
Figure 55 is a pair of three-quarter views of the ink cartridge;
Figure 56 is a three-quarter view of a single ink bladder;
Figures 57a and 57b are lateral and longitudinal sections through the ink cartridge;
25 Figure 58 is a front three-quarter view of the open media tray;
NPP008US
-7-
Figure 59 is a front three-quarter view of the electrical system of the printer;
Figure 60 is a rear three-quarter view of the electrical system;
Figure 61 is a front three-quarter view of the wallprinter with the lower front cover
removed;
5 Figure 62 is a section through the binder assembly;
Figure 63 is a rear three-quarter view of the open glue wheel assembly;
Figure 64 is a section through the binding assembly and the exit hatch;
Figure 65 is a three-dimensional view of an interface module;
Figure 66 is an exploded view of an interface module;
1 0 Figure 67 is a top three-quarter view of the media tray; and
Figure 68 is a section through the top part of the printer.
NPP008US
-8-
DETAILED DESCRIPTION OF PREFERRED AND OTHER EMBODIMENTS
Note: Memjet™ is a trade mark of Silverbrook Research Pry Ltd, Australia.
In the preferred embodiment, the invention is configured to work with the
netpage networked computer system, a detailed overview of which follows. It will be
5 appreciated that not every implementation will necessarily embody all or even most of
the specific details and extensions discussed below in relation to the basic system.
However, the system is described in its most complete form to reduce the need for
external reference when attempting to understand the context in which the preferred
embodiments and aspects of the present invention operate.
10 In brief summary, the preferred form of the netpage system employs a computer
interface in the form of a mapped surface, that is, a physical surface which contains
references to a map of the surface maintained in a computer system. The map references
can be queried by an appropriate sensing device. Depending upon the specific
implementation, the map references may be encoded visibly or invisibly, and defined in
15 such a way that a local query on the mapped surface yields an unambiguous map
reference both within the map and among different maps. The computer system can
contain information about features on the mapped surface, and such information can be
retrieved based on map references supplied by a sensing device used with the mapped
surface. The information thus retrieved can take the form of actions which are initiated
20 by the computer system on behalf of the operator in response to the operator's interaction
with the surface features.
In its preferred form, the netpage system relies on the production of, and human
interaction with, netpages. These are pages of text, graphics and images printed on
ordinary paper, but which work like interactive web pages. Information is encoded on
25 each page using ink which is substantially invisible to the unaided human eye. The ink,
however, and thereby the coded data, can be sensed by an optically imaging pen and
transmitted to the netpage system.
In the preferred form, active buttons and hyperlinks on each page can be
clicked with the pen to request information from the network or to signal preferences to a
30 network server. In one embodiment, text written by hand on a netpage is automatically
recognized and converted to computer text in the netpage system, allowing forms to be
NPP008US
-9-
filled in. In other embodiments, signatures recorded on a netpage are automatically
verified, allowing e-commerce transactions to be securely authorized.
As illustrated in Figure 1, a printed netpage 1 can represent a interactive form
which can be filled in by the user both physically, on the printed page, and
5 "electronically", via communication between the pen and the netpage system. The
example shows a "Request" form containing name and address fields and a submit
button. The netpage consists of graphic data 2 printed using visible ink, and coded data 3
printed as a collection of tags 4 using invisible ink. The corresponding page description
5, stored on the netpage network, describes the individual elements of the netpage. In
10 particular it describes the type and spatial extent (zone) of each interactive element (i.e.
text field or button in the example), to allow the netpage system to correctly interpret
input via the netpage. The submit button 6, for example, has a zone 7 which corresponds
to the spatial extent of the corresponding graphic 8.
As illustrated in Figure 2, the netpage pen 101, a preferred form of which is
1 5 shown in Figures 8 and 9 and described in more detail below, works in conjunction with
a netpage printer 601, an Internet-connected printing appliance for home, office or
mobile use. The pen is wireless and communicates securely with the netpage printer via
a short-range radio link 9.
The netpage printer 601, a preferred form of which is shown in Figures 1 1 to
20 13 and described in more detail below, is able to deliver, periodically or on demand,
personalized newspapers, magazines, catalogs, brochures and other publications, all
printed at high quality as interactive netpages. Unlike a personal computer, the netpage
printer is an appliance which can be, for example, wall-mounted adjacent to an area
where the morning news is first consumed, such as in a user's kitchen, near a breakfast
25 table, or near the household's point of departure for the day. It also comes in tabletop,
desktop, portable and miniature versions.
Netpages printed at their point of consumption combine the ease-of-use of
paper with the timeliness and interactivity of an interactive medium.
As shown in Figure 2, the netpage pen 101 interacts with the coded data on a
30 printed netpage 1 and communicates, via a short-range radio link 9, the interaction to a
netpage printer. The printer 601 sends the interaction to the relevant netpage page server
NPP008US
-10-
10 for interpretation. In appropriate circumstances, the page server sends a corresponding
message to application computer software running on a netpage application server 13.
The application server may in turn send a response which is printed on the originating
printer.
5 The netpage system is made considerably more convenient in the preferred
embodiment by being used in conjunction with high-speed microelectromechanical
system (MEMS) based inkjet (Memjet™) printers. In the preferred form of this
technology, relatively high-speed and high-quality printing is made more affordable to
consumers. In its preferred form, a netpage publication has the physical characteristics of
10 a traditional newsmagazine, such as a set of letter-size glossy pages printed in full color
on both sides, bound together for easy navigation and comfortable handling.
The netpage printer exploits the growing availability of broadband Internet
access. Cable service is available to 95% of households in the United States, and cable
modem service offering broadband Internet access is already available to 20% of these.
1 5 The netpage printer can also operate with slower connections, but with longer delivery
times and lower image quality. Indeed, the netpage system can be enabled using existing
consumer inkjet and laser printers, although the system will operate more slowly and will
therefore be less acceptable from a consumer's point of view. In other embodiments, the
netpage system is hosted on a private intranet. In still other embodiments, the netpage
20 system is hosted on a single computer or computer-enabled device, such as a printer.
Netpage publication servers 14 on the netpage network are configured to
deliver print-quality publications to netpage printers. Periodical publications are
delivered automatically to subscribing netpage printers via pointcasting and multicasting
Internet protocols. Personalized publications are filtered and formatted according to
25 individual user profiles.
A netpage printer can be configured to support any number of pens, and a pen
can work with any number of netpage printers. In the preferred implementation, each
netpage pen has a unique identifier. A household may have a collection of colored
netpage pens, one assigned to each member of the family. This allows each user to
30 maintain a distinct profile with respect to a netpage publication server or application
server.
NPP008US
- 11 -
A netpage pen can also be registered with a netpage registration server 1 1 and
linked to one or more payment card accounts. This allows e-commerce payments to be
securely authorized using the netpage pen. The netpage registration server compares the
signature captured by the netpage pen with a previously registered signature, allowing it
5 to authenticate the user's identity to an e-commerce server. Other biometrics can also be
used to verify identity. A version of the netpage pen includes fingerprint scanning,
verified in a similar way by the netpage registration server.
Although a netpage printer may deliver periodicals such as the morning
newspaper without user intervention, it can be configured never to deliver unsolicited
1 0 junk mail. In its preferred form, it only delivers periodicals from subscribed or otherwise
authorized sources. In this respect, the netpage printer is unlike a fax machine or e-mail
account which is visible to any junk mailer who knows the telephone number or email
address.
1 Netpage System Architecture
15 Each object model in the system is described using a Unified Modeling
Language (UML) class diagram. A class diagram consists of a set of object classes
connected by relationships, and two kinds of relationships are of interest here:
associations and generalizations. An association represents some kind of relationship
between objects, i.e. between instances of classes. A generalization relates actual classes,
20 and can be understood in the following way: if a class is thought of as the set of all
objects of that class, and class A is a generalization of class B, then B is simply a subset
of A. The UML does not directly support second-order modelling - i.e. classes of classes.
Each class is drawn as a rectangle labelled with the name of the class. It
contains a list of the attributes of the class, separated from the name by a horizontal line,
25 and a list of the operations of the class, separated from the attribute list by a horizontal
line. In the class diagrams which follow, however, operations are never modelled.
An association is drawn as a line joining two classes, optionally labelled at
either end with the multiplicity of the association. The default multiplicity is one. An
asterisk (*) indicates a multiplicity of "many", i.e. zero or more. Each association is
30 optionally labelled with its name, and is also optionally labelled at either end with the
role of the corresponding class. An open diamond indicates an aggregation association
NPP008US
- 12-
("is-part-of '), and is drawn at the aggregator end of the association line.
A generalization relationship ("is-a") is drawn as a solid line joining two
classes, with an arrow (in the form of an open triangle) at the generalization end.
When a class diagram is broken up into multiple diagrams, any class which is
duplicated is shown with a dashed outline in all but the main diagram which defines it. It
is shown with attributes only where it is defined.
1.1 Netpages
Netpages are the foundation on which a netpage network is built. They provide
a paper-based user interface to published information and interactive services.
A netpage consists of a printed page (or other surface region) invisibly tagged
with references to an online description of the page. The online page description is
maintained persistently by a netpage page server. The page description describes the
visible layout and content of the page, including text, graphics and images. It also
describes the input elements on the page, including buttons, hyperlinks, and input fields.
A netpage allows markings made with a netpage pen on its surface to be simultaneously
captured and processed by the netpage system.
Multiple netpages can share the same page description. However, to allow
input through otherwise identical pages to be distinguished, each netpage is assigned a
unique page identifier. This page ID has sufficient precision to distinguish between a
very large number of netpages.
Each reference to the page description is encoded in a printed tag. The tag
identifies the unique page on which it appears, and thereby indirectly identifies the page
description. The tag also identifies its own position on the page. Characteristics of the
tags are described in more detail below.
Tags are printed in infrared-absorptive ink on any substrate which is infrared-
reflective, such as ordinary paper. Near-infrared wavelengths are invisible to the human
eye but are easily sensed by a solid-state image sensor with an appropriate filter.
A tag is sensed by an area image sensor in the netpage pen, and the tag data is
transmitted to the netpage system via the nearest netpage printer. The pen is wireless and
communicates with the netpage printer via a short-range radio link. Tags are sufficiently
NPP008US
-13-
small and densely arranged that the pen can reliably image at least one tag even on a
single click on the page. It is important that the pen recognize the page ID and position
on every interaction with the page, since the interaction is stateless. Tags are error-
correctably encoded to make them partially tolerant to surface damage.
The netpage page server maintains a unique page instance for each printed
netpage, allowing it to maintain a distinct set of user-supplied values for input fields in
the page description for each printed netpage.
The relationship between the page description, the page instance, and the
printed netpage is shown in Figure 4. The page instance is associated with both the
netpage printer which printed it and, if known, the netpage user who requested it.
1.2 Netpage Tags
1.2.1 Tag Data Content
In a preferred form, each tag identifies the region in which it appears, and the
location of that tag within the region. A tag may also contain flags which relate to the
region as a whole or to the tag. One or more flag bits may, for example, signal a tag
sensing device to provide feedback indicative of a function associated with the
immediate area of the tag, without the sensing device having to refer to a description of
the region. A netpage pen may, for example, illuminate an "active area" LED when in
the zone of a hyperlink.
As will be more clearly explained below, in a preferred embodiment, each tag
contains an easily recognized invariant structure which aids initial detection, and which
assists in minimizing the effect of any warp induced by the surface or by the sensing
process. The tags preferably tile the entire page, and are sufficiently small and densely
arranged that the pen can reliably image at least one tag even on a single click on the
page. It is important that the pen recognize the page ID and position on every interaction
with the page, since the interaction is stateless.
In a preferred embodiment, the region to which a tag refers coincides with an
entire page, and the region ID encoded in the tag is therefore synonymous with the page
ID of the page on which the tag appears. In other embodiments, the region to which a tag
refers can be an arbitrary subregion of a page or other surface. For example, it can
NPP008US
-14-
coincide with the zone of an interactive element, in which case the region ID can directly
identify the interactive element.
Table 1 - Tag data
Field
Precision (bits)
Region ID
100
Tag ID
16
Flags
4
Total
120
5 Each tag contains 120 bits of information, typically allocated as shown in Table
1. Assuming a maximum tag density of 64 per square inch, a 16-bit tag ID supports a
region size of up to 1024 square inches. Larger regions can be mapped continuously
without increasing the tag ID precision simply by using abutting regions and maps. The
100-bit region ID allows 2 100 (~10 30 or a million trillion trillion) different regions to be
1 0 uniquely identified.
1.2.2 Tag Data Encoding
The 120 bits of tag data are redundantly encoded using a (15, 5) Reed-Solomon
code. This yields 360 encoded bits consisting of 6 codewords of 15 4-bit symbols each.
The (15, 5) code allows up to 5 symbol errors to be corrected per codeword, i.e. it is
1 5 tolerant of a symbol error rate of up to 33% per codeword.
Each 4-bit symbol is represented in a spatially coherent way in the tag, and the
symbols of the six codewords are interleaved spatially within the tag. This ensures that a
burst error (an error affecting multiple spatially adjacent bits) damages a minimum
number of symbols overall and a minimum number of symbols in any one codeword,
20 thus maximising the likelihood that the burst error can be fully corrected.
1 .2.3 Physical Tag Structure
The physical representation of the tag, shown in Figure 5, includes fixed target
structures 15, 16, 17 and variable data areas 18. The fixed target structures allow a
sensing device such as the netpage pen to detect the tag and infer its three-dimensional
25 orientation relative to the sensor. The data areas contain representations of the individual
bits of the encoded tag data.
NPP008US
-15-
To achieve proper tag reproduction, the tag is rendered at a resolution of
256x256 dots. When printed at 1600 dots per inch this yields a tag with a diameter of
about 4 mm. At this resolution the tag is designed to be surrounded by a "quiet area" of
radius 16 dots. Since the quiet area is also contributed by adjacent tags, it only adds 16
dots to the effective diameter of the tag.
The tag includes six target structures. A detection ring 15 allows the sensing
device to initially detect the tag. The ring is easy to detect because it is rotationally
invariant and because a simple correction of its aspect ratio removes most of the effects
of perspective distortion. An orientation axis 16 allows the sensing device to determine
the approximate planar orientation of the tag due to the yaw of the sensor. The
orientation axis is skewed to yield a unique orientation. Four perspective targets 17 allow
the sensing device to infer an accurate two-dimensional perspective transform of the tag
and hence an accurate three-dimensional position and orientation of the tag relative to
the sensor.
All target structures are redundantly large to improve their immunity to noise.
The overall tag shape is circular. This supports, amongst other things, optimal
tag packing on an irregular triangular grid. In combination with the circular detection
ring 15, this makes a circular arrangement of data bits within the tag optimal. As shown
in Figure 48, to maximise its size, each data bit is represented by a radial wedge 510 in
the form of an area bounded by two radial lines 512, a radially inner arc 514 and a
radially outer arc 516. Each wedge 510 has a minimum dimension of 8 dots at 1600 dpi
and is designed so that its base (i.e. its inner arc 514), is at least equal to this minimum
dimension. The radial height of the wedge 510 is always equal to the minimum
dimension. Each 4-bit data symbol is represented by an array 518 of 2x2 wedges 510, as
best shown in Figure 48.
The 1 5 4-bit data symbols of each of the six codewords are allocated to the four
concentric symbol rings 18a to 18d, shown in Figure 5, in interleaved fashion as shown
in Figures 49 to 51. Symbols of first to sixth codewords 520-525 are allocated alternately
in circular progression around the tag.
The interleaving is designed to maximise the average spatial distance between
any two symbols of the same codeword.
NPP008US
- 16-
In order to support "single-click" interaction with a tagged region via a sensing
device, the sensing device must be able to see at least one entire tag in its field of view
no matter where in the region or at what orientation it is positioned. The required
diameter of the field of view of the sensing device is therefore a function of the size and
5 spacing of the tags.
Assuming a circular tag shape, the minimum diameter of the sensor field of
view is obtained when the tags are tiled on a equilateral triangular grid, as shown in
Figure 6.
1.2.4 Tag Image Processing and Decoding
1 0 The tag image processing and decoding performed by a sensing device such as
the netpage pen is shown in Figure 7. While a captured image is being acquired from the
image sensor, the dynamic range of the image is determined (at 20). The center of the
range is then chosen as the binary threshold for the image 21. The image is then
thresholded and segmented into connected pixel regions (i.e. shapes 23) (at 22). Shapes
1 5 which are too small to represent tag target structures are discarded. The size and centroid
of each shape is also computed.
Binary shape moments 25 are then computed (at 24) for each shape, and these
provide the basis for subsequently locating target structures. Central shape moments are
by their nature invariant of position, and can be easily made invariant of scale, aspect
20 ratio and rotation.
The ring target structure 15 is the first to be located (at 26). A ring has the
advantage of being very well behaved when perspective-distorted. Matching proceeds by
aspect-normalizing and rotation-normalizing each shape's moments. Once its second-
order moments are normalized the ring is easy to recognize even if the perspective
25 distortion was significant. The ring's original aspect and rotation 27 together provide a
useful approximation of the perspective transform.
The axis target structure 16 is the next to be located (at 28). Matching proceeds
by applying the ring's normalizations to each shape's moments, and rotation-normalizing
the resulting moments. Once its second-order moments are normalized the axis target is
30 easily recognized. Note that one third order moment is required to disambiguate the two
NPP008US
- 17-
possible orientations of the axis. The shape is deliberately skewed to one side to make
this possible. Note also that it is only possible to rotation-normalize the axis target after
it has had the ring's normalizations applied, since the perspective distortion can hide the
axis target's axis. The axis target's original rotation provides a useful approximation of
the tag's rotation due to pen yaw 29.
The four perspective target structures 17 are the last to be located (at 30). Good
estimates of their positions are computed based on their known spatial relationships to
the ring and axis targets, the aspect and rotation of the ring, and the rotation of the axis.
Matching proceeds by applying the ring's normalizations to each shape's moments. Once
their second-order moments are normalized the circular perspective targets are easy to
recognize, and the target closest to each estimated position is taken as a match. The
original centroids of the four perspective targets are then taken to be the perspective-
distorted corners 31 of a square of known size in tag space, and an eight-degree-of-
freedom perspective transform 33 is inferred (at 32) based on solving the well-
understood equations relating the four tag-space and image-space point pairs (see
Heckbert, P., Fundamentals of Texture Mapping and Image Warping, Masters Thesis,
Dept. of EECS, U. of California at Berkeley, Technical Report No. UCB/CSD 89/516,
June 1989, the contents of which are herein incorporated by cross-reference).
The inferred tag-space to image-space perspective transform is used to project
(at 36) each known data bit position in tag space into image space where the real-valued
position is used to bilinearly interpolate (at 36) the four relevant adjacent pixels in the
input image. The previously computed image threshold 21 is used to threshold the result
to produce the final bit value 37.
Once all 360 data bits 37 have been obtained in this way, each of the six 60-bit
Reed-Solomon codewords is decoded (at 38) to yield 20 decoded bits 39, or 120 decoded
bits in total. Note that the codeword symbols are sampled in codeword order, so that
codewords are implicitly de-interleaved during the sampling process.
The ring target 15 is only sought in a subarea of the image whose relationship
to the image guarantees that the ring, if found, is part of a complete tag. If a complete tag
is not found and successfully decoded, then no pen position is recorded for the current
frame. Given adequate processing power and ideally a non-minimal field of view 193, an
NPP008US
- 18-
altemative strategy involves seeking another tag in the current image.
The obtained tag data indicates the identity of the region containing the tag and
the position of the tag within the region. An accurate position 35 of the pen nib in the
region, as well as the overall orientation 35 of the pen, is then inferred (at 34) from the
perspective transform 33 observed on the tag and the known spatial relationship between
the pen's physical axis and the pen's optical axis.
1.2.5 Tag Map
Decoding a tag results in a region ID, a tag ID, and a tag-relative pen transform.
Before the tag ID and the tag-relative pen location can be translated into an absolute
location within the tagged region, the location of the tag within the region must be
known. This is given by a tag map, a function which maps each tag ID in a tagged region
to a corresponding location. The tag map class diagram is shown in Figure 22, as part of
the netpage printer class diagram.
A tag map reflects the scheme used to tile the surface region with tags, and this
can vary according to surface type. When multiple tagged regions share the same tiling
scheme and the same tag numbering scheme, they can also share the same tag map.
The tag map for a region must be retrievable via the region ID. Thus, given a
region ID, a tag ID and a pen transform, the tag map can be retrieved, the tag ID can be
translated into an absolute tag location within the region, and the tag-relative pen
location can be added to the tag location to yield an absolute pen location within the
region.
1.2.6 Tagging Schemes
Two distinct surface coding schemes are of interest, both of which use the tag
structure described earlier in this section. The preferred coding scheme uses "location-
indicating" tags as already discussed. An alternative coding scheme uses object-
indicating tags.
A location-indicating tag contains a tag ID which, when translated through the
tag map associated with the tagged region, yields a unique tag location within the region.
The tag-relative location of the pen is added to this tag location to yield the location of
the pen within the region. This in turn is used to determine the location of the pen
NPP008US
- 19-
relative to a user interface element in the page description associated with the region.
Not only is the user interface element itself identified, but a location relative to the user
interface element is identified. Location-indicating tags therefore trivially support the
capture of an absolute pen path in the zone of a particular user interface element.
5 An object-indicating tag contains a tag ID which directly identifies a user
interface element in the page description associated with the region. All the tags in the
zone of the user interface element identify the user interface element, making them all
identical and therefore indistinguishable. Object-indicating tags do not, therefore,
support the capture of an absolute pen path. They do, however, support the capture of a
10 relative pen path. So long as the position sampling frequency exceeds twice the
encountered tag frequency, the displacement from one sampled pen position to the next
within a stroke can be unambiguously determined.
With either tagging scheme, the tags function in cooperation with associated
visual elements on the netpage as user interactive elements in that a user can interact
1 5 with the printed page using an appropriate sensing device in order for tag data to be read
by the sensing device and for an appropriate response to be generated in the netpage
system.
1 .3 Document and Page Descriptions
A preferred embodiment of a document and page description class diagram is
20 shown in Figures 25 and 26.
In the netpage system a document is described at three levels. At the most
abstract level the document 836 has a hierarchical structure whose terminal elements 839
are associated with content objects 840 such as text objects, text style objects, image
objects, etc. Once the document is printed on a printer with a particular page size and
25 according to a particular user's scale factor preference, the document is paginated and
otherwise formatted. Formatted terminal elements 835 will in some cases be associated
with content objects which are different from those associated with their corresponding
terminal elements, particularly where the content objects are style-related. Each printed
instance of a document and page is also described separately, to allow input captured
30 through a particular page instance 830 to be recorded separately from input captured
through other instances of the same page description.
NPP008US
-20-
The presence of the most abstract document description on the page server
allows a user to request a copy of a document without being forced to accept the source
document's specific format. The user may be requesting a copy through a printer with a
different page size, for example. Conversely, the presence of the formatted document
description on the page server allows the page server to efficiently interpret user actions
on a particular printed page.
A formatted document 834 consists of a set of formatted page descriptions 5,
each of which consists of a set of formatted terminal elements 835. Each formatted
element has a spatial extent or zone 58 on the page. This defines the active area of input
elements such as hyperlinks and input fields.
A document instance 831 corresponds to a formatted document 834. It consists
of a set of page instances 830, each of which corresponds to a page description 5 of the
formatted document. Each page instance 830 describes a single unique printed netpage 1,
and records the page ID 50 of the netpage. A page instance is not part of a document
instance if it represents a copy of a page requested in isolation.
A page instance consists of a set of terminal element instances 832. An element
instance only exists if it records instance-specific information. Thus, a hyperlink instance
exists for a hyperlink element because it records a transaction ID 55 which is specific to
the page instance, and a field instance exists for a field element because it records input
specific to the page instance. An element instance does not exist, however, for static
elements such as textflows.
A terminal element can be a static element 843, a hyperlink element 844, a
field element 845 or a page server command element 846, as shown in Figure 27. A
static element 843 can be a style element 847 with an associated style object 854, a
textflow element 848 with an associated styled text object 855, an image element 849
with an associated image element 856, a graphic element 850 with an associated graphic
object 857, a video clip element 851 with an associated video clip object 858, an audio
clip element 852 with an associated audio clip object 859, or a script element 853 with
an associated script object 860, as shown in Figure 28.
A page instance has a background field 833 which is used to record any digital
ink captured on the page which does not apply to a specific input element.
NPP008US
-21 -
In the preferred form of the invention, a tag map 811 is associated with each
page instance to allow tags on the page to be translated into locations on the page.
1 .4 The Netpage Network
In a preferred embodiment, a netpage network consists of a distributed set of
5 netpage page servers 10, netpage registration servers 11, netpage ID servers 12, netpage
application servers 13, netpage publication servers 14, and netpage printers 601
connected via a network 19 such as the Internet, as shown in Figure 3.
The netpage registration server 11 is a server which records relationships
between users, pens, printers, applications and publications, and thereby authorizes
1 0 various network activities. It authenticates users and acts as a signing proxy on behalf of
authenticated users in application transactions. It also provides handwriting recognition
services. As described above, a netpage page server 10 maintains persistent information
about page descriptions and page instances. The netpage network includes any number of
page servers, each handling a subset of page instances. Since a page server also
1 5 maintains user input values for each page instance, clients such as netpage printers send
netpage input directly to the appropriate page server. The page server interprets any such
input relative to the description of the corresponding page.
A netpage ID server 12 allocates document IDs 51 on demand, and provides
load-balancing of page servers via its ID allocation scheme.
20 A netpage printer uses the Internet Distributed Name System (DNS), or similar,
to resolve a netpage page ID 50 into the network address of the netpage page server
handling the corresponding page instance.
A netpage application server 13 is a server which hosts interactive netpage
applications. A netpage publication server 14 is an application server which publishes
25 netpage documents to netpage printers. They are described in detail in Section 2.
Netpage servers can be hosted on a variety of network server platforms from
manufacturers such as IBM, Hewlett-Packard, and Sun. Multiple netpage servers can run
concurrently on a single host, and a single server can be distributed over a number of
hosts. Some or all of the functionality provided by netpage servers, and in particular the
30 functionality provided by the ID server and the page server, can also be provided directly
NPP008US
-22-
in a netpage appliance such as a netpage printer, in a computer workstation, or on a local
network.
1 .5 The Netpage Printer
The netpage printer 601 is an appliance which is registered with the netpage
5 system and prints netpage documents on demand and via subscription. Each printer has a
unique printer ID 62, and is connected to the netpage network via a network such as the
Internet, ideally via a broadband connection.
Apart from identity and security settings in non-volatile memory, the netpage
printer contains no persistent storage. As far as a user is concerned, "the network is the
10 computer". Netpages function interactively across space and time with the help of the
distributed netpage page servers 10, independently of particular netpage printers.
The netpage printer receives subscribed netpage documents from netpage
publication servers 14. Each document is distributed in two parts: the page layouts, and
the actual text and image objects which populate the pages. Because of personalization,
1 5 page layouts are typically specific to a particular subscriber and so are pointcast to the
subscriber's printer via the appropriate page server. Text and image objects, on the other
hand, are typically shared with other subscribers, and so are multicast to all subscribers'
printers and the appropriate page servers.
The netpage publication server optimizes the segmentation of document
20 content into pointcasts and multicasts. After receiving the pointcast of a document's page
layouts, the printer knows which multicasts, if any, to listen to.
Once the printer has received the complete page layouts and objects that define
the document to be printed, it can print the document.
The printer rasterizes and prints odd and even pages simultaneously on both
25 sides of the sheet. It contains duplexed print engine controllers 760 and print engines
utilizing Memjet™ printheads 350 for this purpose.
The printing process consists of two decoupled stages: rasterization of page
descriptions, and expansion and printing of page images. The raster image processor
(RIP) consists of one or more standard DSPs 757 running in parallel. The duplexed print
30 engine controllers consist of custom processors which expand, dither and print page
NPP008US
-23-
images in real time, synchronized with the operation of the printheads in the print
engines.
Printers not enabled for IR printing have the option to print tags using IR-
absorptive black ink, although this restricts tags to otherwise empty areas of the page.
5 Although such pages have more limited functionality than IR-printed pages, they are still
classed as netpages.
A normal netpage printer prints netpages on sheets of paper. More specialised
netpage printers may print onto more specialised surfaces, such as globes. Each printer
supports at least one surface type, and supports at least one tag tiling scheme, and hence
10 tag map, for each surface type. The tag map 811 which describes the tag tiling scheme
actually used to print a document becomes associated with that document so that the
document's tags can be correctly interpreted.
Figure 2 shows the netpage printer class diagram, reflecting printer-related
information maintained by a registration server 1 1 on the netpage network.
15 A preferred embodiment of the netpage printer is described in greater detail in
Section 6 below, with reference to Figures 1 1 to 16.
1.5.1 Memjet™ Printheads
The netpage system can operate using printers made with a wide range of
digital printing technologies, including thermal inkjet, piezoelectric inkjet, laser
20 electrophotographic, and others. However, for wide consumer acceptance, it is desirable
that a netpage printer have the following characteristics:
photographic quality color printing
• high quality text printing
high reliability
25 • low printer cost
• low ink cost
• low paper cost
• simple operation
NPP008US
-24-
• nearly silent printing
high printing speed
• simultaneous double sided printing
• compact form factor
5 • low power consumption
No commercially available printing technology has all of these characteristics.
To enable to production of printers with these characteristics, the present
applicant has invented a new print technology, referred to as Memjet™ technology.
Memjet™ is a drop-on-demand inkjet technology that incorporates pagewidth printheads
10 fabricated using microelectromechanical systems (MEMS) technology. Figure 17 shows
a single printing element 300 of a Memjet™ printhead. The netpage wallprinter
incorporates 168960 printing elements 300 to form a 1600 dpi pagewidth duplex printer.
This printer simultaneously prints cyan, magenta, yellow, black, and infrared inks as well
as paper conditioner and ink fixative.
15 The printing element 300 is approximately 110 microns long by 32 microns
wide. Arrays of these printing elements are formed on a silicon substrate 301 that
incorporates CMOS logic, data transfer, timing, and drive circuits (not shown).
Major elements of the printing element 300 are the nozzle 302, the nozzle rim
303, the nozzle chamber 304, the fluidic seal 305, the ink channel rim 306, the lever arm
20 307, the active actuator beam pair 308, the passive actuator beam pair 309, the active
actuator anchor 310, the passive actuator anchor 311, and the ink inlet 312.
The active actuator beam pair 308 is mechanically joined to the passive
actuator beam pair 309 at the join 319. Both beams pairs are anchored at their respective
anchor points 310 and 31 1. The combination of elements 308, 309, 310, 31 1, and 319
25 form a cantilevered electrothermal bend actuator 320.
Figure 18 shows a small part of an array of printing elements 300, including a
cross section 315 of a printing element 300. The cross section 315 is shown without ink,
to clearly show the ink inlet 312 that passes through the silicon wafer 301 .
Figures 19(a), 19(b) and 19(c) show the operating cycle of a Memjet™ printing
NPP008US
-25-
element 300.
Figure 19(a) shows the quiescent position of the ink meniscus 316 prior to
printing an ink droplet. Ink is retained in the nozzle chamber by surface tension at the ink
meniscus 316 and at the fluidic seal 305 formed between the nozzle chamber 304 and the
ink channel rim 306.
While printing, the printhead CMOS circuitry distributes data from the print
engine controller to the correct printing element, latches the data, and buffers the data to
drive the electrodes 318 of the active actuator beam pair 308. This causes an electrical
current to pass through the beam pair 308 for about one microsecond, resulting in Joule
heating. The temperature increase resulting from Joule heating causes the beam pair 308
to expand. As the passive actuator beam pair 309 is not heated, it does not expand,
resulting in a stress difference between the two beam pairs. This stress difference is
partially resolved by the cantilevered end of the electrothermal bend actuator 320
bending towards the substrate 301. The lever arm 307 transmits this movement to the
nozzle chamber 304. The nozzle chamber 304 moves about two microns to the position
shown in Figure 19(b). This increases the ink pressure, forcing ink 321 out of the nozzle
302, and causing the ink meniscus 316 to bulge. The nozzle rim 303 prevents the ink
meniscus 316 from spreading across the surface of the nozzle chamber 304.
As the temperature of the beam pairs 308 and 309 equalizes, the actuator 320
returns to its original position. This aids in the break-off of the ink droplet 317 from the
ink 321 in the nozzle chamber, as shown in Figure 19(c). The nozzle chamber is refilled
by the action of the surface tension at the meniscus 316.
Figure 20 shows a segment of a printhead 350. In a netpage printer, the length
of the printhead is the full width of the paper (typically 210 mm) in the direction 351.
The segment shown is 0.4 mm long (about 0.2% of a complete printhead). When
printing, the paper is moved past the fixed printhead in the direction 352. The printhead
has 6 rows of interdigitated printing elements 300, printing the six colors or types of ink
supplied by the ink inlets 312.
To protect the fragile surface of the printhead during operation, a nozzle guard
wafer 330 is attached to the printhead substrate 301. For each nozzle 302 there is a
corresponding nozzle guard hole 331 through which the ink droplets are fired. To prevent
NPP008US
-26-
the nozzle guard holes 331 from becoming blocked by paper fibers or other debris,
filtered air is pumped through the air inlets 332 and out of the nozzle guard holes during
printing. To prevent ink 321 from drying, the nozzle guard is sealed while the printer is
idle.
5 1.6 The Netpage Pen
The active sensing device of the netpage system is typically a pen 101, which,
using its embedded controller 134, is able to capture and decode IR position tags from a
page via an image sensor. The image sensor is a solid-state device provided with an
appropriate filter to permit sensing at only near-infrared wavelengths. As described in
1 0 more detail below, the system is able to sense when the nib is in contact with the surface,
and the pen is able to sense tags at a sufficient rate to capture human handwriting (i.e. at
200 dpi or greater and 100 Hz or faster). Information captured by the pen is encrypted
and wirelessly transmitted to the printer (or base station), the printer or base station
interpreting the data with respect to the (known) page structure.
15 The preferred embodiment of the netpage pen operates both as a normal
marking ink pen and as a non-marking stylus. The marking aspect, however, is not
necessary for using the netpage system as a browsing system, such as when it is used as
an Internet interface. Each netpage pen is registered with the netpage system and has a
unique pen ID 61. Figure 23 shows the netpage pen class diagram, reflecting pen-related
20 information maintained by a registration server 1 1 on the netpage network.
When either nib is in contact with a netpage, the pen determines its position
and orientation relative to the page. The nib is attached to a force sensor, and the force
on the nib is interpreted relative to a threshold to indicate whether the pen is "up" or
"down". This allows a interactive element on the page to be 'clicked' by pressing with
25 the pen nib, in order to request, say, information from a network. Furthermore, the force
is captured as a continuous value to allow, say, the full dynamics of a signature to be
verified.
The pen determines the position and orientation of its nib on the netpage by
imaging, in the infrared spectrum, an area 193 of the page in the vicinity of the nib. It
30 decodes the nearest tag and computes the position of the nib relative to the tag from the
observed perspective distortion on the imaged tag and the known geometry of the pen
NPP008US
-27-
optics. Although the position resolution of the tag may be low, because the tag density
on the page is inversely proportional to the tag size, the adjusted position resolution is
quite high, exceeding the minimum resolution required for accurate handwriting
recognition.
Pen actions relative to a netpage are captured as a series of strokes. A stroke
consists of a sequence of time-stamped pen positions on the page, initiated by a pen-
down event and completed by the subsequent pen-up event. A stroke is also tagged with
the page ID 50 of the netpage whenever the page ID changes, which, under normal
circumstances, is at the commencement of the stroke.
Each netpage pen has a current selection 826 associated with it, allowing the
user to perform copy and paste operations etc. The selection is timestamped to allow the
system to discard it after a defined time period. The current selection describes a region
of a page instance. It consists of the most recent digital ink stroke captured through the
pen relative to the background area of the page. It is interpreted in an application-specific
manner once it is submitted to an application via a selection hyperlink activation.
Each pen has a current nib 824. This is the nib last notified by the pen to the
system. In the case of the default netpage pen described above, either the marking black
ink nib or the non-marking stylus nib is current. Each pen also has a current nib style
825. This is the nib style last associated with the pen by an application, e.g. in response
to the user selecting a color from a palette. The default nib style is the nib style
associated with the current nib. Strokes captured through a pen are tagged with the
current nib style. When the strokes are subsequently reproduced, they are reproduced in
the nib style with which they are tagged.
Whenever the pen is within range of a printer with which it can communicate,
the pen slowly flashes its "online" LED. When the pen fails to decode a stroke relative to
the page, it momentarily activates its "error" LED. When the pen succeeds in decoding a
stroke relative to the page, it momentarily activates its "ok" LED.
A sequence of captured strokes is referred to as digital ink. Digital ink forms
the basis for the digital exchange of drawings and handwriting, for online recognition of
handwriting, and for online verification of signatures.
NPP008US
-28-
The pen is wireless and transmits digital ink to the netpage printer via a short-
range radio link. The transmitted digital ink is encrypted for privacy and security and
packetized for efficient transmission, but is always flushed on a pen-up event to ensure
timely handling in the printer.
When the pen is out-of-range of a printer it buffers digital ink in internal
memory, which has a capacity of over ten minutes of continuous handwriting. When the
pen is once again within range of a printer, it transfers any buffered digital ink.
A pen can be registered with any number of printers, but because all state data
resides in netpages both on paper and on the network, it is largely immaterial which
printer a pen is communicating with at any particular time.
A preferred embodiment of the pen is described in greater detail in Section 6
below, with reference to Figures 8 to 10.
1 .7 Netpage Interaction
The netpage printer 601 receives data relating to a stroke from the pen 101
when the pen is used to interact with a netpage 1 . The coded data 3 of the tags 4 is read
by the pen when it is used to execute a movement, such as a stroke. The data allows the
identity of the particular page and associated interactive element to be determined and an
indication of the relative positioning of the pen relative to the page to be obtained. The
indicating data is transmitted to the printer, where it resolves, via the DNS, the page ID
50 of the stroke into the network address of the netpage page server 10 which maintains
the corresponding page instance 830. It then transmits the stroke to the page server. If the
page was recently identified in an earlier stroke, then the printer may already have the
address of the relevant page server in its cache. Each netpage consists of a compact page
layout maintained persistently by a netpage page server (see below). The page layout
refers to objects such as images, fonts and pieces of text, typically stored elsewhere on
the netpage network.
When the page server receives the stroke from the pen, it retrieves the page
description to which the stroke applies, and determines which element of the page
description the stroke intersects. It is then able to interpret the stroke in the context of the
type of the relevant element.
NPP008US
-29-
A "click" is a stroke where the distance and time between the pen down
position and the subsequent pen up position are both less than some small maximum. An
object which is activated by a click typically requires a click to be activated, and
accordingly, a longer stroke is ignored. The failure of a pen action, such as a "sloppy"
5 click, to register is indicated by the lack of response from the pen's "ok" LED.
There are two kinds of input elements in a netpage page description: hyperlinks
and form fields. Input through a form field can also trigger the activation of an associated
hyperlink.
1.7.1 Hyperlinks
10 A hyperlink is a means of sending a message to a remote application, and
typically elicits a printed response in the netpage system.
A hyperlink element 844 identifies the application 71 which handles activation
of the hyperlink, a link ID 54 which identifies the hyperlink to the application, an "alias
required" flag which asks the system to include the user's application alias ID 65 in the
1 5 hyperlink activation, and a description which is used when the hyperlink is recorded as a
favorite or appears in the user's history. The hyperlink element class diagram is shown in
Figure 29.
When a hyperlink is activated, the page server sends a request to an application
somewhere on the network. The application is identified by an application ID 64, and the
20 application ID is resolved in the normal way via the DNS. There are three types of
hyperlinks: general hyperlinks 863, form hyperlinks 865, and selection hyperlinks 864,
as shown in Figure 30. A general hyperlink can implement a request for a linked
document, or may simply signal a preference to a server. A form hyperlink submits the
corresponding form to the application. A selection hyperlink submits the current
25 selection to the application. If the current selection contains a single-word piece of text,
for example, the application may return a single-page document giving the word's
meaning within the context in which it appears, or a translation into a different language.
Each hyperlink type is characterized by what information is submitted to the application.
The corresponding hyperlink instance 862 records a transaction ID 55 which
30 can be specific to the page instance on which the hyperlink instance appears. The
NPP008US
-30-
transaction ID can identify user-specific data to the application, for example a "shopping
cart" of pending purchases maintained by a purchasing application on behalf of the user.
The system includes the pen's current selection 826 in a selection hyperlink
activation. The system includes the content of the associated form instance 868 in a form
5 hyperlink activation, although if the hyperlink has its "submit delta" attribute set, only
input since the last form submission is included. The system includes an effective return
path in all hyperlink activations.
A hyperlinked group 866 is a group element 838 which has an associated
hyperlink, as shown in Figure 31. When input occurs through any field element in the
1 0 group, the hyperlink 844 associated with the group is activated. A hyperlinked group can
be used to associate hyperlink behavior with a field such as a checkbox. It can also be
used, in conjunction with the "submit delta" attribute of a form hyperlink, to provide
continuous input to an application. It can therefore be used to support a "blackboard"
interaction model, i.e. where input is captured and therefore shared as soon as it occurs.
15 1.7.2 Forms
A form defines a collection of related input fields used to capture a related set
of inputs through a printed netpage. A form allows a user to submit one or more
parameters to an application software program running on a server.
A form 867 is a group element 838 in the document hierarchy. It ultimately
20 contains a set of terminal field elements 839. A form instance 868 represents a printed
instance of a form. It consists of a set of field instances 870 which correspond to the field
elements 845 of the form. Each field instance has an associated value 871, whose type
depends on the type of the corresponding field element. Each field value records input
through a particular printed form instance, i.e. through one or more printed netpages. The
25 form class diagram is shown in Figure 32.
Each form instance has a status 872 which indicates whether the form is active,
frozen, submitted, void or expired. A form is active when first printed. A form becomes
frozen once it is signed. A form becomes submitted once one of its submission
hyperlinks has been activated, unless the hyperlink has its "submit delta" attribute set. A
30 form becomes void when the user invokes a void form, reset form or duplicate form page
NPP008US
-31 -
command. A form expires when the time the form has been active exceeds the form's
specified lifetime. While the form is active, form input is allowed. Input through a form
which is not active is instead captured in the background field 833 of the relevant page
instance. When the form is active or frozen, form submission is allowed. Any attempt to
submit a form when the form is not active or frozen is rejected, and instead elicits an
form status report.
Each form instance is associated (at 59) with any form instances derived from
it, thus providing a version history. This allows all but the latest version of a form in a
particular time period to be excluded from a search.
All input is captured as digital ink. Digital ink 873 consists of a set of
timestamped stroke groups 874, each of which consists of a set of styled strokes 875.
Each stroke consists of a set of timestamped pen positions 876, each of which also
includes pen orientation and nib force. The digital ink class diagram is shown in Figure
33.
A field element 845 can be a checkbox field 877, a text field 878, a drawing
field 879, or a signature field 880. The field element class diagram is shown in Figure
34. Any digital ink captured in a field's zone 58 is assigned to the field.
A checkbox field has an associated boolean value 881, as shown in Figure 35.
Any mark (a tick, a cross, a stroke, a fill zigzag, etc.) captured in a checkbox field's zone
causes a true value to be assigned to the field's value.
A text field has an associated text value 882, as shown in Figure 36. Any digital
ink captured in a text field's zone is automatically converted to text via online
handwriting recognition, and the text is assigned to the field's value. Online handwriting
recognition is well-understood (see, for example, Tappert, C, C.Y. Suen and T.
Wakahara, "The State of the Art in On-Line Handwriting Recognition", IEEE
Transactions on Pattern Analysis and Machine Intelligence, Vol.12, No.8, August 1990,
the contents of which are herein incorporated by cross-reference).
A signature field has an associated digital signature value 883, as shown in
Figure 37. Any digital ink captured in a signature field's zone is automatically verified
with respect to the identity of the owner of the pen, and a digital signature of the content
NPP008US
-32-
of the form of which the field is part is generated and assigned to the field's value. The
digital signature is generated using the pen user's private signature key specific to the
application which owns the form. Online signature verification is well-understood (see,
for example, Plamondon, R. and G. Lorette, "Automatic Signature Verification and
5 Writer Identification - The State of the Art", Pattern Recognition, Vol.22, No.2, 1989,
the contents of which are herein incorporated by cross-reference).
A field element is hidden if its "hidden" attribute is set. A hidden field element
does not have an input zone on a page and does not accept input. It can have an
associated field value which is included in the form data when the form containing the
1 0 field is submitted.
"Editing" commands, such as strike-throughs indicating deletion, can also be
recognized in form fields.
Because the handwriting recognition algorithm works "online" (i.e. with access
to the dynamics of the pen movement), rather than "offline" (i.e. with access only to a
15 bitmap of pen markings), it can recognize run-on discretely-written characters with
relatively high accuracy, without a writer-dependent training phase. A writer-dependent
model of handwriting is automatically generated over time, however, and can be
generated up-front if necessary,
Digital ink, as already stated, consists of a sequence of strokes. Any stroke
20 which starts in a particular element's zone is appended to that element's digital ink
stream, ready for interpretation. Any stroke not appended to an object's digital ink
stream is appended to the background field's digital ink stream.
Digital ink captured in the background field is interpreted as a selection
gesture. Circumscription of one or more objects is generally interpreted as a selection of
25 the circumscribed objects, although the actual interpretation is application-specific.
Table 2 summarises these various pen interactions with a netpage.
Table 2 - Summary of pen interactions with a netpage
Object
Type
Pen input
Action
Hyperlink
General
Click
Submit action to application
Form
Click
Submit form to application
NPP008US
-33-
Selection
Click
Submit selection to application
Form field
Checkbox
Any mark
Assign true to field
Text
Handwriting
Convert digital ink to text; assign
text to field
Drawing
Digital ink
Assign digital ink to field
Signature
Signature
Verify digital ink signature;
generate digital signature of form;
assign digital signature to field
None
Circumscription
Assign digital ink to current
selection
The system maintains a current selection for each pen. The selection consists
simply of the most recent stroke captured in the background field. The selection is
cleared after an inactivity timeout to ensure predictable behavior.
5 The raw digital ink captured in every field is retained on the netpage page
server and is optionally transmitted with the form data when the form is submitted to the
application. This allows the application to interrogate the raw digital ink should it
suspect the original conversion, such as the conversion of handwritten text. This can, for
example, involve human intervention at the application level for forms which fail certain
10 application-specific consistency checks. As an extension to this, the entire background
area of a form can be designated as a drawing field. The application can then decide, on
the basis of the presence of digital ink outside the explicit fields of the form, to route the
form to a human operator, on the assumption that the user may have indicated
amendments to the filled-in fields outside of those fields.
15 Figure 38 shows a flowchart of the process of handling pen input relative to a
netpage. The process consists of receiving (at 884) a stroke from the pen; identifying (at
885) the page instance 830 to which the page ID 50 in the stroke refers; retrieving (at
886) the page description 5; identifying (at 887) a formatted element 839 whose zone 58
the stroke intersects; determining (at 888) whether the formatted element corresponds to
20 a field element, and if so appending (at 892) the received stroke to the digital ink of the
field value 871, interpreting (at 893) the accumulated digital ink of the field, and
determining (at 894) whether the field is part of a hyperlmked group 866 and if so
activating (at 895) the associated hyperlink; alternatively determining (at 889) whether
the formatted element corresponds to a hyperlink element and if so activating (at 895)
25 the corresponding hyperlink; alternatively, in the absence of an input field or hyperlink,
NPP008US
-34-
appending (at 890) the received stroke to the digital ink of the background field 833; and
copying (at 891) the received stroke to the current selection 826 of the current pen, as
maintained by the registration server.
Figure 38a shows a detailed flowchart of step 893 in the process shown in
5 Figure 38, where the accumulated digital ink of a field is interpreted according to the
type of the field. The process consists of determining (at 896) whether the field is a
checkbox and (at 897) whether the digital ink represents a checkmark, and if so
assigning (at 898) a true value to the field value; alternatively determining (at 899)
whether the field is a text field and if so converting (at 900) the digital ink to computer
10 text, with the help of the appropriate registration server, and assigning (at 901) the
converted computer text to the field value; alternatively determining (at 902) whether the
field is a signature field and if so verifying (at 903) the digital ink as the signature of the
pen's owner, with the help of the appropriate registration server, creating (at 904) a
digital signature of the contents of the corresponding form, also with the help of the
15 registration server and using the pen owner's private signature key relating to the
corresponding application, and assigning (at 905) the digital signature to the field value.
1.7.3 Page Server Commands
A page server command is a command which is handled locally by the page
server. It operates directly on form, page and document instances.
20 A page server command 907 can be a void form command 908, a duplicate
form command 909, a reset form command 910, a get form status command 911, a
duplicate page command 912, a reset page command 913, a get page status command
914, a duplicate document command 915, a reset document command 916, or a get
document status command 917, as shown in Figure 39.
25 A void form command voids the corresponding form instance. A duplicate
form command voids the corresponding form instance and then produces an active
printed copy of the current form instance with field values preserved. The copy contains
the same hyperlink transaction IDs as the original, and so is indistinguishable from the
original to an application. A reset form command voids the corresponding form instance
30 and then produces an active printed copy of the form instance with field values
discarded. A get form status command produces a printed report on the status of the
NPP008US
-35-
corresponding form instance, including who published it, when it was printed, for whom
it was printed, and the form status of the form instance.
Since a form hyperlink instance contains a transaction ID, the application has to
be involved in producing a new form instance. A button requesting a new form instance
is therefore typically implemented as a hyperlink.
A duplicate page command produces a printed copy of the corresponding page
instance with the background field value preserved. If the page contains a form or is part
of a form, then the duplicate page command is interpreted as a duplicate form command.
A reset page command produces a printed copy of the corresponding page instance with
the background field value discarded. If the page contains a form or is part of a form,
then the reset page command is interpreted as a reset form command. A get page status
command produces a printed report on the status of the corresponding page instance,
including who published it, when it was printed, for whom it was printed, and the status
of any forms it contains or is part of.
The netpage logo which appears on every netpage is usually associated with a
duplicate page element.
When a page instance is duplicated with field values preserved, field values are
printed in their native form, i.e. a checkmark appears as a standard checkmark graphic,
and text appears as typeset text. Only drawings and signatures appear in their original
form, with a signature accompanied by a standard graphic indicating successful signature
verification.
A duplicate document command produces a printed copy of the corresponding
document instance with background field values preserved. If the document contains any
forms, then the duplicate document command duplicates the forms in the same way a
duplicate form command does. A reset document command produces a printed copy of
the corresponding document instance with background field values discarded. If the
document contains any forms, then the reset document command resets the forms in the
same way a reset form command does. A get document status command produces a
printed report on the status of the corresponding document instance, including who
published it, when it was printed, for whom it was printed, and the status of any forms it
contains.
NPP008US
-36-
If the page server command's "on selected" attribute is set, then the command
operates on the page identified by the pen's current selection rather than on the page
containing the command. This allows a menu of page server commands to be printed. If
the target page doesn't contain a page server command element for the designated page
5 server command, then the command is ignored.
An application can provide application-specific handling by embedding the
relevant page server command element in a hyperlinked group. The page server activates
the hyperlink associated with the hyperlinked group rather than executing the page server
command.
10 A page server command element is hidden if its "hidden" attribute is set. A
hidden command element does not have an input zone on a page and so cannot be
activated directly by a user. It can, however, be activated via a page server command
embedded in a different page, if that page server command has its "on selected" attribute
set.
15 1 .8 Standard Features of Netpages
In the preferred form, each netpage is printed with the netpage logo at the
bottom to indicate that it is a netpage and therefore has interactive properties. The logo
also acts as a copy button. In most cases pressing the logo produces a copy of the page.
In the case of a form, the button produces a copy of the entire form. And in the case of a
20 secure document, such as a ticket or coupon, the button elicits an explanatory note or
advertising page.
The default single-page copy function is handled directly by the relevant
netpage page server. Special copy functions are handled by linking the logo button to an
application.
25 1.9 User Help System
In a preferred embodiment, the netpage printer has a single button labelled
"Help". When pressed it elicits a single page of information, including:
• status of printer connection
• status of printer consumables
NPP008US
• top-level help menu
• document function menu
• top-level netpage network directory
The help menu provides a hierarchical manual on how to use the netpage
5 system.
The document function menu includes the following functions:
• print a copy of a document
• print a clean copy of a form
print the status of a document
10 A document function is initiated by simply pressing the button and then
touching any page of the document. The status of a document indicates who published it
and when, to whom it was delivered, and to whom and when it was subsequently
submitted as a form.
The netpage network directory allows the user to navigate the hierarchy of
1 5 publications and services on the network. As an alternative, the user can call the netpage
network "900" number "yellow pages" and speak to a human operator. The operator can
locate the desired document and route it to the user's printer. Depending on the
document type, the publisher or the user pays the small "yellow pages" service fee.
The help page is obviously unavailable if the printer is unable to print. In this
20 case the "error" light is lit and the user can request remote diagnosis over the network.
2 Personalized Publication Model
In the following description, news is used as a canonical publication example
to illustrate personalization mechanisms in the netpage system. Although news is often
used in the limited sense of newspaper and newsmagazine news, the intended scope in
25 the present context is wider.
In the netpage system, the editorial content and the advertising content of a
news publication are personalized using different mechanisms. The editorial content is
personalized according to the reader's explicitly stated and implicitly captured interest
NPP008US
-38-
profile. The advertising content is personalized according to the reader's locality and
demographic.
2.1 Editorial Personalization
A subscriber can draw on two kinds of news sources: those that deliver news
5 publications, and those that deliver news streams. While news publications are
aggregated and edited by the publisher, news streams are aggregated either by a news
publisher or by a specialized news aggregator. News publications typically correspond to
traditional newspapers and newsmagazines, while news streams can be many and varied:
a "raw" news feed from a news service, a cartoon strip, a freelance writer's column, a
1 0 friend' s bulletin board, or the reader' s own e-mail.
The netpage publication server supports the publication of edited news
publications as well as the aggregation of multiple news streams. By handling the
aggregation and hence the formatting of news streams selected directly by the reader, the
server is able to place advertising on pages over which it otherwise has no editorial
1 5 control.
The subscriber builds a daily newspaper by selecting one or more contributing
news publications, and creating a personalized version of each. The resulting daily
editions are printed and bound together into a single newspaper. The various members of
a household typically express their different interests and tastes by selecting different
20 daily publications and then customizing them.
For each publication, the reader optionally selects specific sections. Some
sections appear daily, while others appear weekly. The daily sections available from The
New York Times online, for example, include "Page One Plus", "National",
"International", "Opinion", "Business", "Arts/Living", "Technology", and "Sports". The
25 set of available sections is specific to a publication, as is the default subset.
The reader can extend the daily newspaper by creating custom sections, each
one drawing on any number of news streams. Custom sections might be created for e-
mail and friends' announcements ("Personal"), or for monitoring news feeds for specific
topics ("Alerts" or "Clippings").
30 For each section, the reader optionally specifies its size, either qualitatively
NPP008US
-39-
(e.g. short, medium, or long), or numerically (i.e. as a limit on its number of pages), and
the desired proportion of advertising, either qualitatively (e.g. high, normal, low, none),
or numerically (i.e. as a percentage).
The reader also optionally expresses a preference for a large number of shorter
5 articles or a small number of longer articles. Each article is ideally written (or edited) in
both short and long forms to support this preference.
An article may also be written (or edited) in different versions to match the
expected sophistication of the reader, for example to provide children's and adults'
versions. The appropriate version is selected according to the reader's age. The reader
10 can specify a "reading age" which takes precedence over their biological age.
The articles which make up each section are selected and prioritized by the
editors, and each is assigned a useful lifetime. By default they are delivered to all
relevant subscribers, in priority order, subject to space constraints in the subscribers'
editions.
15 In sections where it is appropriate, the reader may optionally enable
collaborative filtering. This is then applied to articles which have a sufficiently long
lifetime. Each article which qualifies for collaborative filtering is printed with rating
buttons at the end of the article. The buttons can provide an easy choice (e.g. "liked" and
"disliked'), making it more likely that readers will bother to rate the article.
20 Articles with high priorities and short lifetimes are therefore effectively
considered essential reading by the editors and are delivered to most relevant
subscribers.
The reader optionally specifies a serendipity factor, either qualitatively (e.g. do
or don't surprise me), or numerically. A high serendipity factor lowers the threshold used
25 for matching during collaborative filtering. A high factor makes it more likely that the
corresponding section will be filled to the reader's specified capacity. A different
serendipity factor can be specified for different days of the week.
The reader also optionally specifies topics of particular interest within a
section, and this modifies the priorities assigned by the editors.
30 The speed of the reader's Internet connection affects the quality at which
NPP008US
-40-
images can be delivered. The reader optionally specifies a preference for fewer images or
smaller images or both. If the number or size of images is not reduced, then images may
be delivered at lower quality (i.e. at lower resolution or with greater compression).
At a global level, the reader specifies how quantities, dates, times and monetary
5 values are localized. This involves specifying whether units are imperial or metric, a
local timezone and time format, and a local currency, and whether the localization
consist of in situ translation or annotation. These preferences are derived from the
reader's locality by default.
To reduce reading difficulties caused by poor eyesight, the reader optionally
1 0 specifies a global preference for a larger presentation. Both text and images are scaled
accordingly, and less information is accommodated on each page.
The language in which a news publication is published, and its corresponding
text encoding, is a property of the publication and not a preference expressed by the user.
However, the netpage system can be configured to provide automatic translation services
15 in various guises.
2.2 Advertising Localization and Targeting
The personalization of the editorial content directly affects the advertising
content, because advertising is typically placed to exploit the editorial context. Travel
ads, for example, are more likely to appear in a travel section than elsewhere. The value
20 of the editorial content to an advertiser (and therefore to the publisher) lies in its ability
to attract large numbers of readers with the right demographics.
Effective advertising is placed on the basis of locality and demographics.
Locality determines proximity to particular services, retailers etc., and particular interests
and concerns associated with the local community and environment. Demographics
25 determine general interests and preoccupations as well as likely spending patterns.
A news publisher's most profitable product is advertising "space", a multi-
dimensional entity determined by the publication's geographic coverage, the size of its
readership, its readership demographics, and the page area available for advertising.
In the netpage system, the netpage publication server computes the
30 approximate multi-dimensional size of a publication's saleable advertising space on a
NPP008US
-41 -
per-section basis, taking into account the publication's geographic coverage, the
section's readership, the size of each reader's section edition, each reader's advertising
proportion, and each reader's demographic.
In comparison with other media, the netpage system allows the advertising
5 space to be defined in greater detail, and allows smaller pieces of it to be sold separately.
It therefore allows it to be sold at closer to its true value.
For example, the same advertising "slot" can be sold in varying proportions to
several advertisers, with individual readers' pages randomly receiving the advertisement
of one advertiser or another, overall preserving the proportion of space sold to each
1 0 advertiser.
The netpage system allows advertising to be linked directly to detailed product
information and online purchasing. It therefore raises the intrinsic value of the
advertising space.
Because personalization and localization are handled automatically by netpage
1 5 publication servers, an advertising aggregator can provide arbitrarily broad coverage of
both geography and demographics. The subsequent disaggregation is efficient because it
is automatic. This makes it more cost-effective for publishers to deal with advertising
aggregators than to directly capture advertising. Even though the advertising aggregator
is taking a proportion of advertising revenue, publishers may find the change profit-
20 neutral because of the greater efficiency of aggregation. The advertising aggregator acts
as an intermediary between advertisers and publishers, and may place the same
advertisement in multiple publications.
It is worth noting that ad placement in a netpage publication can be more
complex than ad placement in the publication's traditional counterpart, because the
25 publication's advertising space is more complex. While ignoring the full complexities of
negotiations between advertisers, advertising aggregators and publishers, the preferred
form of the netpage system provides some automated support for these negotiations,
including support for automated auctions of advertising space. Automation is particularly
desirable for the placement of advertisements which generate small amounts of income,
30 such as small or highly localized advertisements.
NPP008US
-42-
Once placement has been negotiated, the aggregator captures and edits the
advertisement and records it on a netpage ad server. Correspondingly, the publisher
records the ad placement on the relevant netpage publication server. When the netpage
publication server lays out each user's personalized publication, it picks the relevant
5 advertisements from the netpage ad server.
2.3 User Profiles
2.3.1 Information Filtering
The personalization of news and other publications relies on an assortment of
user-specific profile information, including:
10 • publication customizations
• collaborative filtering vectors
• contact details
• presentation preferences
The customization of a publication is typically publication-specific, and so the
1 5 customization information is maintained by the relevant netpage publication server.
A collaborative filtering vector consists of the user's ratings of a number of
news items. It is used to correlate different users' interests for the purposes of making
recommendations. Although there are benefits to maintaining a single collaborative
filtering vector independently of any particular publication, there are two reasons why it
20 is more practical to maintain a separate vector for each publication: there is likely to be
more overlap between the vectors of subscribers to the same publication than between
those of subscribers to different publications; and a publication is likely to want to
present its users' collaborative filtering vectors as part of the value of its brand, not to be
found elsewhere. Collaborative filtering vectors are therefore also maintained by the
25 relevant netpage publication server.
Contact details, including name, street address, ZIP Code, state, country,
telephone numbers, are global by nature, and are maintained by a netpage registration
server.
Presentation preferences, including those for quantities, dates and times, are
NPP008US
-43-
likewise global and maintained in the same way.
The localization of advertising relies on the locality indicated in the user's
contact details, while the targeting of advertising relies on personal information such as
date of birth, gender, marital status, income, profession, education, or qualitative
5 derivatives such as age range and income range.
For those users who choose to reveal personal information for advertising
purposes, the information is maintained by the relevant netpage registration server. In the
absence of such information, advertising can be targeted on the basis of the demographic
associated with the user's ZIP or ZIP+4 Code.
1 0 Each user, pen, printer, application provider and application is assigned its own
unique identifier, and the netpage registration server maintains the relationships between
them, as shown in Figures 21, 22, 23 and 24. For registration purposes, a publisher is a
special kind of application provider, and a publication is a special kind of application.
Each user 800 may be authorized to use any number of printers 802, and each
1 5 printer may allow any number of users to use it. Each user has a single default printer (at
66), to which periodical publications are delivered by default, whilst pages printed on
demand are delivered to the printer through which the user is interacting. The server
keeps track of which publishers a user has authorized to print to the user's default
printer. A publisher does not record the ID of any particular printer, but instead resolves
20 the ID when it is required.
When a user subscribes 808 to a publication 807, the publisher 806 (i.e.
application provider 803) is authorized to print to a specified printer or the user's default
printer. This authorization can be revoked at any time by the user. Each user may have
several pens 801, but a pen is specific to a single user. If a user is authorized to use a
25 particular printer, then that printer recognizes any of the user's pens.
The pen ID is used to locate the corresponding user profile maintained by a
particular netpage registration server, via the DNS in the usual way.
A Web terminal 809 can be authorized to print on a particular netpage printer,
allowing Web pages and netpage documents encountered during Web browsing to be
30 conveniently printed on the nearest netpage printer.
NPP008US
-44-
The netpage system can collect, on behalf of a printer provider, fees and
commissions on income earned through publications printed on the provider's printers.
Such income can include advertising fees, click-through fees, e-commerce commissions,
and transaction fees. If the printer is owned by the user, then the user is the printer
5 provider.
Each user also has a netpage account 820 which is used to accumulate micro-
debits and credits (such as those described in the preceding paragraph); contact details
815, including name, address and telephone numbers; global preferences 816, including
privacy, delivery and localization settings; any number of biometric records 817,
10 containing the user's encoded signature 818, fingerprint 819 etc; a handwriting model
819 automatically maintained by the system; and SET payment card accounts 821 with
which e-commerce payments can be made.
2.3.2 Favorites List
A netpage user can maintain a list 922 of "favorites" - links to useful
15 documents etc. on the netpage network. The list is maintained by the system on the
user's behalf. It is organized as a hierarchy of folders 924, a preferrred embodiment of
which is shown in the class diagram in Figure 41 .
2.3.3 History List
The system maintains a history list 929 on each user's behalf, containing links
20 to documents etc. accessed by the user through the netpage system. It is organized as a
date-ordered list, a preferred embodiment of which is shown in the class diagram in
Figure 42.
2.4 Intelligent Page Layout
The netpage publication server automatically lays out the pages of each user's
25 personalized publication on a section-by-section basis. Since most advertisements are in
the form of pre-formatted rectangles, they are placed on the page before the editorial
content.
The advertising ratio for a section can be achieved with wildly varying
advertising ratios on individual pages within the section, and the ad layout algorithm
30 exploits this. The algorithm is configured to attempt to co-locate closely tied editorial
NPP008US
-45-
and advertising content, such as placing ads for roofing material specifically within the
publication because of a special feature on do-it-yourself roofing repairs.
The editorial content selected for the user, including text and associated images
and graphics, is then laid out according to various aesthetic rules.
5 The entire process, including the selection of ads and the selection of editorial
content, must be iterated once the layout has converged, to attempt to more closely
achieve the user's stated section size preference. The section size preference can,
however, be matched on average over time, allowing significant day-to-day variations.
2.5 Document Format
10 Once the document is laid out, it is encoded for efficient distribution and
persistent storage on the netpage network.
The primary efficiency mechanism is the separation of information specific to a
single user's edition and information shared between multiple users' editions. The
specific information consists of the page layout. The shared information consists of the
1 5 objects to which the page layout refers, including images, graphics, and pieces of text.
A text object contains fully-formatted text represented in the Extensible
Markup Language (XML) using the Extensible Stylesheet Language (XSL). XSL
provides precise control over text formatting independently of the region into which the
" text is being set, which in this case is being provided by the layout. The text object
20 contains embedded language codes to enable automatic translation, and embedded
hyphenation hints to aid with paragraph formatting.
An image object encodes an image in the JPEG 2000 wavelet-based
compressed image format. A graphic object encodes a 2D graphic in Scalable Vector
Graphics (SVG) format.
25 The layout itself consists of a series of placed image and graphic objects, linked
textflow objects through which text objects flow, hyperlinks and input fields as
described above, and watermark regions. These layout objects are summarized in Table
3. The layout uses a compact format suitable for efficient distribution and storage.
NPP008US
-46-
Table 3 - netpage layout objects
Layout
object
Attribute
Format of
linked object
Image
Position
Image object ID
JPEG 2000
Graphic
Position
Graphic object ID
SVG
Textflow
Textflow ID
Zone
-
Optional text object ID
XML/XSL
Hyperlink
Type
Zone
Application ID, etc.
Field
Type
Meaning
Zone
Watermark
Zone
2.6 Document Distribution
As described above, for purposes of efficient distribution and persistent storage
5 on the netpage network, a user-specific page layout is separated from the shared objects
to which it refers.
When a subscribed publication is ready to be distributed, the netpage
publication server allocates, with the help of the netpage ID server 12, a unique ID for
each page, page instance, document, and document instance.
10 The server computes a set of optimized subsets of the shared content and
creates a multicast channel for each subset, and then tags each user-specific layout with
the names of the multicast channels which will carry the shared content used by that
layout. The server then pointcasts each user's layouts to that user's printer via the
appropriate page server, and when the pointcasting is complete, multicasts the shared
15 content on the specified channels. After receiving its pointcast, each page server and
printer subscribes to the multicast channels specified in the page layouts. During the
multicasts, each page server and printer extracts from the multicast streams those objects
referred to by its page layouts. The page servers persistently archive the received page
layouts and shared content.
20 Once a printer has received all the objects to which its page layouts refer, the
NPP008US
-47-
printer re-creates the fully-populated layout and then rasterizes and prints it.
Under normal circumstances, the printer prints pages faster than they can be
delivered. Assuming a quarter of each page is covered with images, the average page has
a size of less than 400KB. The printer can therefore hold in excess of 100 such pages in
5 its internal 64MB memory, allowing for temporary buffers etc. The printer prints at a
rate of one page per second. This is equivalent to 400KB or about 3Mbit of page data per
second, which is similar to the highest expected rate of page data delivery over a
broadband network.
Even under abnormal circumstances, such as when the printer runs out of
1 0 paper, it is likely that the user will be able to replenish the paper supply before the
printer's 100-page internal storage capacity is exhausted.
However, if the printer's internal memory does fill up, then the printer will be
unable to make use of a multicast when it first occurs. The netpage publication server
therefore allows printers to submit requests for re-multicasts. When a critical number of
15 requests is received or a timeout occurs, the server re-multicasts the corresponding
shared objects.
Once a document is printed, a printer can produce an exact duplicate at any
time by retrieving its page layouts and contents from the relevant page server.
2.7 On-Demand Documents
20 When a netpage document is requested on demand, it can be personalized and
delivered in much the same way as a periodical. However, since there is no shared
content, delivery is made directly to the requesting printer without the use of multicast.
When a non-netpage document is requested on demand, it is not personalized,
and it is delivered via a designated netpage formatting server which reformats it as a
25 netpage document. A netpage formatting server is a special instance of a netpage
publication server. The netpage formatting server has knowledge of various Internet
document formats, including Adobe's Portable Document Format (PDF), and Hypertext
Markup Language (HTML). In the case of HTML, it can make use of the higher
resolution of the printed page to present Web pages in a multi-column format, with a
30 table of contents. It can automatically include all Web pages directly linked to the
NPP008US
-48-
requested page. The user can tune this behavior via a preference.
The netpage formatting server makes standard netpage behavior, including
interactivity and persistence, available on any Internet document, no matter what its
origin and format. It hides knowledge of different document formats from both the
5 netpage printer and the netpage page server, and hides knowledge of the netpage system
from Web servers.
3 Security
3.1 Cryptography
Cryptography is used to protect sensitive information, both in storage and in
1 0 transit, and to authenticate parties to a transaction. There are two classes of cryptography
in widespread use: secret-key cryptography and public-key cryptography. The netpage
network uses both classes of cryptography.
Secret-key cryptography, also referred to as symmetric cryptography, uses the
same key to encrypt and decrypt a message. Two parties wishing to exchange messages
1 5 must first arrange to securely exchange the secret key.
Public-key cryptography, also referred to as asymmetric cryptography, uses two
encryption keys. The two keys are mathematically related in such a way that any message
encrypted using one key can only be decrypted using the other key. One of these keys is
then published, while the other is kept private. The public key is used to encrypt any
20 message intended for the holder of the private key. Once encrypted using the public key,
a message can only be decrypted using the private key. Thus two parties can securely
exchange messages without first having to exchange a secret key. To ensure that the
private key is secure, it is normal for the holder of the private key to generate the key
pair.
25 Public-key cryptography can be used to create a digital signature. The holder of
the private key can create a known hash of a message and then encrypt the hash using the
private key. Anyone can then verify that the encrypted hash constitutes the "signature" of
the holder of the private key with respect to that particular message by decrypting the
encrypted hash using the public key and verifying the hash against the message. If the
30 signature is appended to the message, then the recipient of the message can verify both
NPP008US
-49-
that the message is genuine and that it has not been altered in transit.
To make public-key cryptography work, there has to be a way to distribute
public keys which prevents impersonation. This is normally done using certificates and
certificate authorities. A certificate authority is a trusted third party which authenticates
5 the connection between a public key and someone's identity. The certificate authority
verifies the person's identity by examining identity documents, and then creates and
signs a digital certificate containing the person's identity details and public key. Anyone
who trusts the certificate authority can use the public key in the certificate with a high
degree of certainty that it is genuine. They just have to verify that the certificate has
1 0 indeed been signed by the certificate authority, whose public key is well-known.
In most transaction environments, public-key cryptography is only used to
create digital signatures and to securely exchange secret session keys. Secret-key
cryptography is used for all other purposes.
In the following discussion, when reference is made to the secure transmission
15 of information between a netpage printer and a server, what actually happens is that the
printer obtains the server's certificate, authenticates it with reference to the certificate
authority, uses the public key-exchange key in the certificate to exchange a secret session
key with the server, and then uses the secret session key to encrypt the message data. A
session key, by definition, can have an arbitrarily short lifetime.
20 3.2 Netpage Printer Security
Each netpage printer is assigned a pair of unique identifiers at time of
manufacture which are stored in read-only memory in the printer and in the netpage
registration server database. The first ID 62 is public and uniquely identifies the printer
on the netpage network. The second ID is secret and is used when the printer is first
25 registered on the network.
When the printer connects to the netpage network for the first time after
installation, it creates a signature public/private key pair. It transmits the secret ID and
the public key securely to the netpage registration server. The server compares the secret
ID against the printer's secret ID recorded in its database, and accepts the registration if
30 the IDs match. It then creates and signs a certificate containing the printer's public ID
NPP008US
-50-
and public signature key, and stores the certificate in the registration database.
The netpage registration server acts as a certificate authority for netpage
printers, since it has access to secret information allowing it to verify printer identity.
When a user subscribes to a publication, a record is created in the netpage
5 registration server database authorizing the publisher to print the publication to the user' s
default printer or a specified printer. Every document sent to a printer via a page server is
addressed to a particular user and is signed by the publisher using the publisher's private
signature key. The page server verifies, via the registration database, that the publisher is
authorized to deliver the publication to the specified user. The page server verifies the
10 signature using the publisher's public key, obtained from the publisher's certificate
stored in the registration database.
The netpage registration server accepts requests to add printing authorizations
to the database, so long as those requests are initiated via a pen registered to the printer.
3.3 Netpage Pen Security
-| 5 Each netpage pen is assigned a unique identifier at time of manufacture which
is stored in read-only memory in the pen and in the netpage registration server database.
The pen ID 61 uniquely identifies the pen on the netpage network.
A netpage pen can "know" a number of netpage printers, and a printer can
"know" a number of pens. A pen communicates with a printer via a radio frequency
20 signal whenever it is within range of the printer. Once a pen and printer are registered,
they regularly exchange session keys. Whenever the pen transmits digital ink to the
printer, the digital ink is always encrypted using the appropriate session key. Digital ink
is never transmitted in the clear.
A pen stores a session key for every printer it knows, indexed by printer ID,
25 and a printer stores a session key for every pen it knows, indexed by pen ID. Both have a
large but finite storage capacity for session keys, and will forget a session key on a least-
recently-used basis if necessary.
When a pen comes within range of a printer, the pen and printer discover
whether they know each other. If they don't know each other, then the printer determines
30 whether it is supposed to know the pen. This might be, for example, because the pen
NPP008US
-51 -
belongs to a user who is registered to use the printer. If the printer is meant to know the
pen but doesn't, then it initiates the automatic pen registration procedure. If the printer
isn't meant to know the pen, then it agrees with the pen to ignore it until the pen is
placed in a charging cup, at which time it initiates the registration procedure.
5 In addition to its public ID, the pen contains a secret key-exchange key. The
key-exchange key is also recorded in the netpage registration server database at time of
manufacture. During registration, the pen transmits its pen ID to the printer, and the
printer transmits the pen ID to the netpage registration server. The server generates a
session key for the printer and pen to use, and securely transmits the session key to the
1 0 printer. It also transmits a copy of the session key encrypted with the pen's key-exchange
key. The printer stores the session key internally, indexed by the pen ID, and transmits
the encrypted session key to the pen. The pen stores the session key internally, indexed
by the printer ID.
Although a fake pen can impersonate a pen in the pen registration protocol,
1 5 only a real pen can decrypt the session key transmitted by the printer.
When a previously unregistered pen is first registered, it is of limited use until
it is linked to a user. A registered but "un-owned" pen is only allowed to be used to
request and fill in netpage user and pen registration forms, to register a new user to
which the new pen is automatically linked, or to add a new pen to an existing user.
20 The pen uses secret-key rather than public-key encryption because of hardware
performance constraints in the pen.
3.4 Secure Documents
The netpage system supports the delivery of secure documents such as tickets
and coupons. The netpage printer includes a facility to print watermarks, but will only do
25 so on request from publishers who are suitably authorized. The publisher indicates its
authority to print watermarks in its certificate, which the printer is able to authenticate.
The "watermark" printing process uses an alternative dither matrix in specified
"watermark" regions of the page. Back-to-back pages contain mirror-image watermark
regions which coincide when printed. The dither matrices used in odd and even pages'
30 watermark regions are designed to produce an interference effect when the regions are
NPP008US
-52-
viewed together, achieved by looking through the printed sheet.
The effect is similar to a watermark in that it is not visible when looking at only
one side of the page, and is lost when the page is copied by normal means.
Pages of secure documents cannot be copied using the built-in netpage copy
5 mechanism described in Section 1.9 above. This extends to copying netpages on
netpage-aware photocopiers.
Secure documents are typically generated as part of e-commerce transactions.
They can therefore include the user's photograph which was captured when the user
registered biometric information with the netpage registration server, as described in
10 Section 2.
When presented with a secure netpage document, the recipient can verify its
authenticity by requesting its status in the usual way. The unique ID of a secure
document is only valid for the lifetime of the document, and secure document IDs are
allocated non-contiguously to prevent their prediction by opportunistic forgers. A secure
15 document verification pen can be developed with built-in feedback on verification
failure, to support easy point-of-presentation document verification.
Clearly neither the watermark nor the user's photograph are secure in a
cryptographic sense. They simply provide a significant obstacle to casual forgery. Online
document verification, particularly using a verification pen, provides an added level of
20 security where it is needed, but is still not entirely immune to forgeries.
3.5 Non-Repudiation
In the netpage system, forms submitted by users are delivered reliably to forms
handlers and are persistently archived on netpage page servers. It is therefore impossible
for recipients to repudiate delivery.
25 E-commerce payments made through the system, as described in Section 4, are
also impossible for the payee to repudiate.
4 Electronic Commerce Model
4.1 Secure Electronic Transaction (SET)
The netpage system uses the Secure Electronic Transaction (SET) system as
NPP008US
-53-
one of its payment systems. SET, having been developed by MasterCard and Visa, is
organized around payment cards, and this is reflected in the terminology. However,
much of the system is independent of the type of accounts being used.
In SET, cardholders and merchants register with a certificate authority and are
5 issued with certificates containing their public signature keys. The certificate authority
verifies a cardholder's registration details with the card issuer as appropriate, and verifies
a merchant's registration details with the acquirer as appropriate. Cardholders and
merchants store their respective private signature keys securely on their computers.
During the payment process, these certificates are used to mutually authenticate a
1 0 merchant and cardholder, and to authenticate them both to the payment gateway.
SET has not yet been adopted widely, partly because cardholder maintenance of
keys and certificates is considered burdensome. Interim solutions which maintain
cardholder keys and certificates on a server and give the cardholder access via a
password have met with some success.
15 4.2 SET Payments
In the netpage system the netpage registration server acts as a proxy for the
netpage user (i.e. the cardholder) in SET payment transactions.
The netpage system uses biometrics to authenticate the user and authorize SET
payments. Because the system is pen-based, the biometric used is the user's on-line
20 signature, consisting of time-varying pen position and pressure. A fingerprint biometric
can also be used by designing a fingerprint sensor into the pen, although at a higher cost.
The type of biometric used only affects the capture of the biometric, not the
authorization aspects of the system.
The first step to being able to make SET payments is to register the user's
25 biometric with the netpage registration server. This is done in a controlled environment,
for example a bank, where the biometric can be captured at the same time as the user's
identity is verified. The biometric is captured and stored in the registration database,
linked to the user's record. The user's photograph is also optionally captured and linked
to the record. The SET cardholder registration process is completed, and the resulting
30 private signature key and certificate are stored in the database. The user's payment card
NPP008US
-54-
information is also stored, giving the netpage registration server enough information to
act as the user's proxy in any SET payment transaction.
When the user eventually supplies the biometric to complete a payment, for
example by signing a netpage order form, the printer securely transmits the order
5 information, the pen ID and the biometric data to the netpage registration server. The
server verifies the biometric with respect to the user identified by the pen ID, and from
then on acts as the user's proxy in completing the SET payment transaction.
4.3 Micro-Payments
The netpage system includes a mechanism for micro-payments, to allow the
1 0 user to be conveniently charged for printing low-cost documents on demand and for
copying copyright documents, and possibly also to allow the user to be reimbursed for
expenses incurred in printing advertising material. The latter depends on the level of
subsidy already provided to the user.
When the user registers for e-commerce, a network account is established
1 5 which aggregates micro-payments. The user receives a statement on a regular basis, and
can settle any outstanding debit balance using the standard payment mechanism.
The network account can be extended to aggregate subscription fees for
periodicals, which would also otherwise be presented to the user in the form of
individual statements.
20 4.4 Transactions
When a user requests a netpage in a particular application context, the
application is able to embed a user-specific transaction ID 55 in the page. Subsequent
input through the page is tagged with the transaction ID, and the application is thereby
able to establish an appropriate context for the user's input.
25 When input occurs through a page which is not user-specific, however, the
application must use the user's unique identity to establish a context. A typical example
involves adding items from a pre-printed catalog page to the user's virtual "shopping
cart". To protect the user's privacy, however, the unique user ID 60 known to the
netpage system is not divulged to applications. This is to prevent different application
30 providers from easily correlating independently accumulated behavioral data.
NPP008US
-55-
The netpage registration server instead maintains an anonymous relationship
between a user and an application via a unique alias ID 65, as shown in Figure 24.
Whenever the user activates a hyperlink tagged with the "registered" attribute, the
netpage page server asks the netpage registration server to translate the associated
5 application ID 64, together with the pen ID 61, into an alias ID 65. The alias ID is then
submitted to the hyperlink's application.
The application maintains state information indexed by alias ID, and is able to
retrieve user-specific state information without knowledge of the global identity of the
user.
1 0 The system also maintains an independent certificate and private signature key
for each of a user's applications, to allow it to sign application transactions on behalf of
the user using only application-specific information.
To assist the system in routing product bar code (UPC) "hyperlink" activations,
the system records a favorite application on behalf of the user for any number of product
1 5 types.
Each application is associated with an application provider, and the system
maintains an account on behalf of each application provider, to allow it to credit and
debit the provider for click-through fees etc.
An application provider can be a publisher of periodical subscribed content.
20 The system records the user's willingness to receive the subscribed publication, as well
as the expected frequency of publication.
4.5 Resource Descriptions and Copyright
A preferred embodiment of a resource description class diagram is shown in
Figure 40.
25 Each document and content object may be described by one or more resource
descriptions 842. Resource descriptions use the Dublin Core metadata element set,
which is designed to facilitate discovery of electronic resources. Dublin Core metadata
conforms to the World Wide Web Consortium (W3C) Resource Description Framework
(RDF).
30 A resource description may identify rights holders 920. The netpage system
NPP008US
-56-
automatically transfers copyright fees from users to rights holders when users print
copyright content.
5 Communications Protocols
A communications protocol defines an ordered exchange of messages between
5 entities. In the netpage system, entities such as pens, printers and servers utilise a set of
defined protocols to cooperatively handle user interaction with the netpage system.
Each protocol is illustrated by way of a sequence diagram in which the
horizontal dimension is used to represent message flow and the vertical dimension is
used to represent time. Each entity is represented by a rectangle containing the name of
1 0 the entity and a vertical column representing the lifeline of the entity. During the time an
entity exists, the lifeline is shown as a dashed line. During the time an entity is active,
the lifeline is shown as a double line. Because the protocols considered here do not
create or destroy entities, lifelines are generally cut short as soon as an entity ceases to
participate in a protocol.
15 5.1 Subscription Delivery Protocol
A preferred embodiment of a subscription delivery protocol is shown in Figure
43.
A large number of users may subscribe to a periodical publication. Each user's
edition may be laid out differently, but many users' editions will share common content
20 such as text objects and image objects. The subscription delivery protocol therefore
delivers document structures to individual printers via pointcast, but delivers shared
content objects via multicast.
The application (i.e. publisher) first obtains a document ID 51 for each
document from an ID server 12. It then sends each document structure, including its
25 document ID and page descriptions, to the page server 10 responsible for the document's
newly allocated ID. It includes its own application ID 64, the subscriber's alias ID 65,
and the relevant set of multicast channel names. It signs the message using its private
signature key.
The page server uses the application ID and alias ID to obtain from the
30 registration server the corresponding user ID 60, the user's selected printer ID 62 (which
NPP008US
-57-
may be explicitly selected for the application, or may be the user's default printer), and
the application's certificate.
The application's certificate allows the page server to verify the message
signature. The page server's request to the registration server fails if the application ID
and alias ID don't together identify a subscription 808.
The page server then allocates document and page instance IDs and forwards
the page descriptions, including page IDs 50, to the printer. It includes the relevant set of
multicast channel names for the printer to listen to.
It then returns the newly allocated page IDs to the application for future
reference.
Once the application has distributed all of the document structures to the
subscribers' selected printers via the relevant page servers, it multicasts the various
subsets of the shared objects on the previously selected multicast channels. Both page
servers and printers monitor the appropriate multicast channels and receive their required
content objects. They are then able to populate the previously pointcast document
structures. This allows the page servers to add complete documents to their databases,
and it allows the printers to print the documents.
5,2 Hyperlink Activation Protocol
A preferred embodiment of a hyperlink activation protocol is shown in Figure
45.
When a user clicks on a netpage with a netpage pen, the pen communicates the
click to the nearest netpage printer 601. The click identifies the page and a location on
the page. The printer already knows the ID 61 of the pen from the pen connection
protocol.
The printer determines, via the DNS, the network address of the page server
10a handling the particular page ID 50. The address may already be in its cache if the
user has recently interacted with the same page. The printer then forwards the pen ID, its
own printer ID 62, the page ID and click location to the page server.
The page server loads the page description 5 identified by the page ID and
determines which input element's zone 58, if any, the click lies in. Assuming the
NPP008US
-58-
relevant input element is a hyperlink element 844, the page server then obtains the
associated application ID 64 and link ID 54, and determines, via the DNS, the network
address of the application server hosting the application 71.
The page server uses the pen ID 61 to obtain the corresponding user ID 60 from
5 the registration server 1 1, and then allocates a globally unique hyperlink request ID 52
and builds a hyperlink request 934. The hyperlink request class diagram is shown in
Figure 44. The hyperlink request records the IDs of the requesting user and printer, and
identifies the clicked hyperlink instance 862. The page server then sends its own server
ID 53, the hyperlink request ID, and the link ID to the application.
10 The application produces a response document according to application-
specific logic, and obtains a document ID 51 from an ID server 12. It then sends the
document to the page server 10b responsible for the document's newly allocated ID,
together with the requesting page server's ID and the hyperlink request ID.
The second page server sends the hyperlink request ID and application ID to
1 5 the first page server to obtain the corresponding user ID and printer ID 62. The first page
server rejects the request if the hyperlink request has expired or is for a different
application.
The second page server allocates document instance and page IDs 50, returns
the newly allocated page IDs to the application, adds the complete document to its own
20 database, and finally sends the page descriptions to the requesting printer.
The hyperlink instance may include a meaningful transaction ID 55, in which
case the first page server includes the transaction ID in the message sent to the
application. This allows the application to establish a transaction-specific context for the
hyperlink activation.
25 If the hyperlink requires a user alias, i.e. its "alias required" attribute is set, then
the first page server sends both the pen ID 61 and the hyperlink's application ID 64 to
the registration server 1 1 to obtain not just the user ID corresponding to the pen ID but
also the alias ID 65 corresponding to the application ID and the user ID. It includes the
alias ID in the message sent to the application, allowing the application to establish a
30 user-specific context for the hyperlink activation.
NPP008US
-59-
5.3 Handwriting Recognition Protocol
When a user draws a stroke on a netpage with a netpage pen, the pen
communicates the stroke to the nearest netpage printer. The stroke identifies the page
and a path on the page.
5 The printer forwards the pen ID 61, its own printer ID 62, the page ID 50 and
stroke path to the page server 10 in the usual way.
The page server loads the page description 5 identified by the page ID and
determines which input element's zone 58, if any, the stroke intersects. Assuming the
relevant input element is a text field 878, the page server appends the stroke to the text
1 0 field's digital ink.
After a period of inactivity in the zone of the text field, the page server sends
the pen ID and the pending strokes to the registration server 1 1 for interpretation. The
registration server identifies the user corresponding to the pen, and uses the user's
accumulated handwriting model 822 to interpret the strokes as handwritten text. Once it
1 5 has converted the strokes to text, the registration server returns the text to the requesting
page server. The page server appends the text to the text value of the text field.
5.4 Signature Verification Protocol
Assuming the input element whose zone the stroke intersects is a signature
field 880, the page server 10 appends the stroke to the signature field's digital ink.
20 After a period of inactivity in the zone of the signature field, the page server
sends the pen ID 61 and the pending strokes to the registration server 1 1 for verification.
It also sends the application ID 64 associated with the form of which the signature field
is part, as well as the form ID 56 and the current data content of the form. The
registration server identifies the user corresponding to the pen, and uses the user's
25 dynamic signature biometric 81 8 to verify the strokes as the user's signature. Once it has
verified the signature, the registration server uses the application ID 64 and user ID 60 to
identify the user's application-specific private signature key. It then uses the key to
generate a digital signature of the form data, and returns the digital signature to the
requesting page server. The page server assigns the digital signature to the signature field
30 and sets the associated form's status to frozen.
NPP008US
-60-
The digital signature includes the alias ID 65 of the corresponding user. This
allows a single form to capture multiple users' signatures.
5.5 Form Submission Protocol
A preferred embodiment of a form submission protocol is shown in Figure 46.
5 Form submission occurs via a form hyperlink activation. It thus follows the
protocol defined in Section 5.2, with some form-specific additions.
In the case of a form hyperlink, the hyperlink activation message sent by the
page server 10 to the application 71 also contains the form ID 56 and the current data
content of the form. If the form contains any signature fields, then the application
10 verifies each one by extracting the alias ID 65 associated with the corresponding digital
signature and obtaining the corresponding certificate from the registration server 11.
5.6 Commission Payment Protocol
A preferred embodiment of a commission payment protocol is shown in Figure
47.
15 In an e-commerce environment, fees and commissions may be payable from an
application provider to a publisher on click-throughs, transactions and sales.
Commissions on fees and commissions on commissions may also be payable from the
publisher to the provider of the printer.
The hyperlink request ID 52 is used to route a fee or commission credit from
20 the target application provider 70a (e.g. merchant) to the source application provider 70b
(i.e. publisher), and from the source application provider 70b to the printer provider 72.
The target application receives the hyperlink request ID from the page server 10
when the hyperlink is first activated, as described in Section 5.2. When the target
application needs to credit the source application provider, it sends the application
25 provider credit to the original page server together with the hyperlink request ID. The
page server uses the hyperlink request ID to identify the source application, and sends
the credit on to the relevant registration server 1 1 together with the source application ID
64, its own server ID 53, and the hyperlink request ID. The registration server credits the
corresponding application provider's account 827. It also notifies the application
NPP008US
-61 -
provider.
If the application provider needs to credit the printer provider, it sends the
printer provider credit to the original page server together with the hyperlink request ID.
The page server uses the hyperlink request ID to identify the printer, and sends the credit
5 on to the relevant registration server together with the printer ID. The registration server
credits the corresponding printer provider account 814.
The source application provider is optionally notified of the identity of the
target application provider, and the printer provider of the identity of the source
application provider.
10 6. Netpage Pen Description
6.1 Pen Mechanics
Referring to Figures 8 and 9, the pen, generally designated by reference
numeral 101, includes a housing 102 in the form of a plastics moulding having walls 103
defining an interior space 104 for mounting the pen components. The pen top 105 is in
1 5 operation rotatably mounted at one end 106 of the housing 1 02. A semi-transparent cover
107 is secured to the opposite end 108 of the housing 102. The cover 107 is also of
moulded plastics, and is formed from semi-transparent material in order to enable the
user to view the status of the LED mounted within the housing 102. The cover 107
includes a main part 109 which substantially surrounds the end 108 of the housing 102
20 and a projecting portion 110 which projects back from the main part 109 and fits within
a corresponding slot 111 formed in the walls 103 of the housing 102. A radio antenna
1 12 is mounted behind the projecting portion 1 10, within the housing 102. Screw threads
113 surrounding an aperture 1 13A on the cover 107 are arranged to receive a metal end
piece 114, including corresponding screw threads 115. The metal end piece 114 is
25 removable to enable ink cartridge replacement.
Also mounted within the cover 107 is a tri-color status LED 1 16 on a flex PCB
117. The antenna 112 is also mounted on the flex PCB 117. The status LED 116 is
mounted at the top of the pen 101 for good all-around visibility.
The pen can operate both as a normal marking ink pen and as a non-marking
30 stylus. An ink pen cartridge 118 with nib 119 and a stylus 120 with stylus nib 121 are
NPP008US
-62-
mounted side by side within the housing 102. Either the ink cartridge nib 119 or the
stylus nib 121 can be brought forward through open end 122 of the metal end piece 1 14,
by rotation of the pen top 105. Respective slider blocks 123 and 124 are mounted to the
ink cartridge 118 and stylus 120, respectively. A rotatable cam barrel 125 is secured to
5 the pen top 105 in operation and arranged to rotate therewith. The cam barrel 125
includes a cam 126 in the form of a slot within the walls 181 of the cam barrel. Cam
followers 127 and 128 projecting from slider blocks 123 and 124 fit within the cam slot
126. On rotation of the cam barrel 125, the slider blocks 123 or 124 move relative to
each other to project either the pen nib 1 19 or stylus nib 121 out through the hole 122 in
10 the metal end piece 114. The pen 101 has three states of operation. By turning the top
105 through 90° steps, the three states are:
Stylus 120 nib 121 out;
• Ink cartridge 1 1 8 nib 1 1 9 out; and
Neither ink cartridge 1 18 nib 1 19 out nor stylus 120 nib 121 out.
15 A second flex PCB 129, is mounted on an electronics chassis 130 which sits
within the housing 102. The second flex PCB 129 mounts an infrared LED 131 for
providing infrared radiation for projection onto the surface. An image sensor 132 is
provided mounted on the second flex PCB 129 for receiving reflected radiation from the
surface. The second flex PCB 129 also mounts a radio frequency chip 133, which
20 includes an RF transmitter and RF receiver, and a controller chip 134 for controlling
operation of the pen 101. An optics block 135 (formed from moulded clear plastics) sits
within the cover 107 and projects an infrared beam onto the surface and receives images
onto the image sensor 132. Power supply wires 136 connect the components on the
second flex PCB 129 to battery contacts 137 which are mounted within the cam barrel
25 125. A terminal 138 connects to the battery contacts 137 and the cam barrel 125. A three
volt rechargeable battery 139 sits within the cam barrel 125 in contact with the battery
contacts. An induction charging coil 140 is mounted about the second flex PCB 129 to
enable recharging of the battery 139 via induction. The second flex PCB 129 also
mounts an infrared LED 143 and infrared photodiode 144 for detecting displacement in
30 the cam barrel 125 when either the stylus 1 20 or the ink cartridge 1 1 8 is used for writing,
in order to enable a determination of the force being applied to the surface by the pen nib
NPP008US
-63-
119 or stylus nib 121. The IR photodiode 144 detects light from the IR LED 143 via
reflectors (not shown) mounted on the slider blocks 123 and 124.
Rubber grip pads 141 and 142 are provided towards the end 108 of the housing
102 to assist gripping the pen 101, and top 105 also includes a clip 142 for clipping the
5 pen 101 to a pocket.
6.2 Pen Controller
The pen 101 is arranged to determine the position of its nib (stylus nib 121 or
ink cartridge nib 1 19) by imaging, in the infrared spectrum, an area of the surface in the
vicinity of the nib. It records the location data from the nearest location tag, and is
10 arranged to calculate the distance of the nib 121 or 119 from the location tab utilising
optics 135 and controller chip 134. The controller chip 134 calculates the orientation of
the pen and the nib-to-tag distance from the perspective distortion observed on the
imaged tag.
Utilising the RF chip 133 and antenna 1 12 the pen 101 can transmit the digital
15 ink data (which is encrypted for security and packaged for efficient transmission) to the
computing system.
When the pen is in range of a receiver, the digital ink data is transmitted as it is
formed. When the pen 101 moves out of range, digital ink data is buffered within the pen
101 (the pen 101 circuitry includes a buffer arranged to store digital ink data for
20 approximately 12 minutes of the pen motion on the surface) and can be transmitted later.
The controller chip 134 is mounted on the second flex PCB 129 in the pen 101 .
Figure 10 is a block diagram illustrating in more detail the architecture of the controller
chip 134. Figure 10 also shows representations of the RF chip 133, the image sensor 132,
the tri-color status LED 116, the IR illumination LED 131, the IR force sensor LED 143,
25 and the force sensor photodiode 144.
The pen controller chip 134 includes a controlling processor 145. Bus 146
enables the exchange of data between components of the controller chip 134. Flash
memory 147 and a 512 KB DRAM 148 are also included. An analog-to-digital converter
149 is arranged to convert the analog signal from the force sensor photodiode 144 to a
30 digital signal.
NPP008US
-64-
An image sensor interface 152 interfaces with the image sensor 132. A
transceiver controller 153 and base band circuit 154 are also included to interface with
the RF chip 133 which includes an RF circuit 155 and RF resonators and inductors 156
connected to the antenna 112.
5 The controlling processor 145 captures and decodes location data from tags
from the surface via the image sensor 132, monitors the force sensor photodiode 144,
controls the LEDs 116, 131 and 143, and handles short-range radio communication via
the radio transceiver 153. It is a medium-performance (~40MHz) general-purpose RISC
processor.
10 The processor 145, digital transceiver components (transceiver controller 153
and baseband circuit 154), image sensor interface 152, flash memory 147 and 512KB
DRAM 148 are integrated in a single controller ASIC. Analog RF components (RF
circuit 155 and RF resonators and inductors 156) are provided in the separate RF chip.
The image sensor is a 215x215 pixel CCD (such a sensor is produced by
15 Matsushita Electronic Corporation, and is described in a paper by Itakura, K T
Nobusada, N Okusenya, R Nagayoshi, and M Ozaki, "A 1mm 50k-Pixel IT CCD Image
Sensor for Miniature Camera System", IEEE Transactions on Electronic Devices, Volt
47, number 1 , January 2000, which is incorporated herein by reference) with an IR filter.
The controller ASIC 134 enters a quiescent state after a period of inactivity
20 when the pen 1 01 is not in contact with a surface. It incorporates a dedicated circuit 1 50
which monitors the force sensor photodiode 144 and wakes up the controller 134 via the
power manager 151 on a pen-down event.
The radio transceiver communicates in the unlicensed 900MHz band normally
used by cordless telephones, or alternatively in the unlicensed 2.4GHz industrial,
25 scientific and medical (ISM) band, and uses frequency hopping and collision detection to
provide interference-free communication.
In an alternative embodiment, the pen incorporates an Infrared Data
Association (IrDA) interface for short-range communication with a base station or
netpage printer.
30 In a further embodiment, the pen 101 includes a pair of orthogonal
NPP008US
-65-
accelerometers mounted in the normal plane of the pen 101 axis. The accelerometers 190
are shown in Figures 9 and 10 in ghost outline.
The provision of the accelerometers enables this embodiment of the pen 101 to
sense motion without reference to surface location tags, allowing the location tags to be
5 sampled at a lower rate. Each location tag ID can then identify an obj ect of interest rather
than a position on the surface. For example, if the object is a user interface input element
(e.g. a command button), then the tag ID of each location tag within the area of the input
element can directly identify the input element.
The acceleration measured by the accelerometers in each of the x and y
10 directions is integrated with respect to time to produce an instantaneous velocity and
position.
Since the starting position of the stroke is not known, only relative positions
within a stroke are calculated. Although position integration accumulates errors in the
sensed acceleration, accelerometers typically have high resolution, and the time duration
15 of a stroke, over which errors accumulate, is short.
7. Netpage Printer Description
7.1 Printer Mechanics
The vertically-mounted netpage wallprinter 601 is shown fully assembled in
Figures 11 and 12. As best shown in Figures 12, 12a and 68, it prints netpages on A4
20 sized media using duplexed 8/2" Memjet™ print engines 602 and 603. It uses a straight
paper path with the paper 604 passing through duplexed print engines 602 and 603
which print both sides of a sheet simultaneously, in full color and with full bleed. A
multi-DSP raster image processor (RIP) rasterizes pages to internal memory, and a pair
of custom print engine controllers expand, dither and print page images to the duplexed
25 printheads in real time.
An integral binding assembly 605 applies a strip of glue along one edge of each
printed sheet, allowing it to adhere to the previous sheet when pressed against it. This
creates a final bound document 618 which can range in thickness from one sheet to
several hundred sheets. The binding assembly will be considered in close detail below
30 with particular reference to Figures 62, 63 and 64.
NPP008US
-66-
Referring to Figures 11, 12, 12a, 13 and 53 to 58, the wallprinter 601 consists
of a main chassis 606, which accommodates all major components and assemblies. As
best shown in Figure 58, it has a pivoting media tray 607 on the front upper portion,
which is covered by a front molding 608 and handle molding 609. The front molding
5 608, handle molding 609 and lower front molding 610 can vary in color, texture and
finish to make the product more appealing to consumers. They simply clip onto the front
of the wallprinter 601.
Figures 59 and 60 show the wallprinter electrical system in isolation. A flexible
printed circuit board (flex PCB) 611 runs from the media tray 607 to the main PCB 612.
1 0 It includes four different color LEDs 613, 614, 615 and 616 and a push button 617. The
LEDs show through the front molding and indicate "on" 613, "ink out" 614, "paper out"
615, and "error" 616. The push button 617 elicits printed "help" in the form of usage
instructions, printer and consumable status information, and a directory of resources on
the netpage network.
1 5 Printed, bound documents 61 8 exit through the base of the wallprinter 601 into
a clear, plastic, removable collection tray 619. This is discussed in greater detail below
with specific reference to Figure 64.
The wallprinter 601 is powered by an internal 110V/220V power supply 620
and has a metal mounting plate 621 that is secured to a wall or stable vertical surface by
20 four screws. Plunged keyhole slot details 622 in the metal plate 621 allow for four
spigots mounted on the rear of the printer to hook onto the plate. The wallprinter 601 is
prevented from being lifted off by a screw that locates the chassis molding 606 to the
plate 621 at one position behind the media tray 607.
Referring to Figures 53, 65 and 66, the side of the wallprinter 601 includes a
25 module bay 624 which accommodates a network interface module 625 which allows the
printer to be connected to the netpage network and to a local computer or network. The
interface module 625 can be selected and installed in the factory or in the field to provide
the interfaces required by the user. The modules may have common connector options,
such as: IEEE 1394 (Firewire) connection, standard Centronics printer port connection or
30 a combined USB2 649 and Ethernet 650 connection. This allows the consumer to
connect the wallprinter 601 to a computer or use it as a network printer. Figure 66 shows
NPP008US
-67-
the exploded assembly of the module 625. The interface module PCB 651, (with gold
contact edge strips) plugs directly into the main wallprinter PCB 612 via an edge
connector 654. The different connector configurations are accommodated in the module
design by use of a tool insert 652. Finger recesses 653 on either side of the module 625
5 allow for easy manual insertion or removal.
Turning to Figure 68, the main PCB 612 is attached to the rear of the chassis
606. The board 612 interfaces through the chassis molding 606 to the interface module
625. The PCB 612 also carries the necessary peripheral electronics to the Memjet™
printheads 705. This includes a main CPU with two 32MB DRAMs, flash memory,
10 IEEE 1394 interface chip, six motor controllers, various sensor connectors, interface
module PCB edge connector, power management, internal/external data connectors and a
QA chip.
Figure 58 shows the front hatch access to the paper 604 and the ink cartridge
627. Referring to Figure 67, paper 604 is placed into a hinged top tray 607 and pressed
1 5 down onto a sprung platen 666. The tray 607 is mounted to the chassis 606 via hinges
700. Each hinge has a base, a hinge lever and a hinge side. Pivots on the base and
paper/media tray 607 engage the lever and side such that the paper/media tray 607 rotates
in a manner that avoids kinking the supply hoses 646.
The paper 604 is positioned under edge guides 667 before being closed and is
20 automatically registered to one side of the tray 607 by action of a metal spring part 668.
An ink cartridge 627 connects into a pivoting ink connector molding 628 via a series of
self-sealing connectors 629. The connectors 629 transmit ink, air and glue to their
separate locations. The ink connector molding 628 contains a sensor, which detects a QA
chip on the ink cartridge and verifies identification prior to printing. When the front
25 hatch is sensed closed, a release mechanism allows the sprung platen 666 to push the
paper 604 against a motorized media pick-up roller assembly 626.
Figure 54, shows the complete assembly of the replaceable ink cartridge 627. It
has bladders or chambers for storing fixative 644, adhesive 630, and cyan 631, magenta
632, yellow 633, black 634 and infrared 635 inks. The cartridge 627 also contains a
30 micro air filter 636 in a base molding 637. As shown in Figure 13, the micro air filter
636 interfaces with an air pump 638 inside the printer via a hose 639. This provides
NPP008US
-68-
filtered air to the printheads 705 to prevent ingress of micro particles into the Memjet™
printheads 705 which may clog the nozzles. By incorporating the air filter 636 within the
cartridge 627, the operational life of the filter is effectively linked to the life of the
cartridge. This ensures that the filter is replaced together with the cartridge rather than
5 relying on the user to clean or replace the filter at the required intervals. Furthermore, the
adhesive and infrared ink are replenished together with the visible inks and air filter
thereby reducing how frequently the printer operation is interrupted because of the
depletion of a consumable material.
The cartridge 627 has a thin wall casing 640. The ink bladders 631 to 635 and
10 fixitive bladder 644 are suspended within the casing by a pin 645 which hooks the
cartridge together. The single glue bladder 630 is accommodated in the base molding
637. This is a fully recyclable product with a capacity for printing and gluing 3000 pages
(1500 sheets).
Referring to Figures 12, 12a, 59, 60 and 68, the motorized media pick-up roller
1 5 assembly 626 pushes the top sheet directly from the media tray 607 past a paper sensor
(not shown) on the first print engine 602 into the duplexed Memjet™ printhead
assembly.
Two Memjet™ print engines 602 and 603 are mounted in an opposing in-line
sequential configuration along the straight paper path. The paper 604 is drawn into the
20 first print engine 602 by integral, powered pick-up rollers 626. The position and size of
the paper 604 is sensed and full bleed printing commences.
Fixative is printed simultaneously to aid drying in the shortest possible time.
As best shown in Figure 12a, the Memjet™ print engines 602 and 603 include
a rotary capping, blotting and platen device 669. The capping device seals the Memjet™
25 printheads 705 when not in use. It uncaps and rotates to produce an integral blotter,
which is used for absorbing ink fired from the printheads 705 during routine printer
startup maintenance. It simultaneously moves an internal capping device inside the
Memjet™ printhead 705 that allows air to flow into the protective nozzle shield area.
The third rotation of the device moves a platen surface into place, which supports one
30 side of the sheet 604 during printing.
NPP008US
-69-
The paper exits the first Memjet™ print engine 602 through a set of powered
exit spike wheels (aligned along the straight paper path), which acts against a rubberized
roller. These spike wheels contact the 'wet' printed surface and continue to feed the
sheet 604 into the second Memjet™ print engine 603.
5 This second print engine 603 is mounted the opposite way up to the first in
order to print the underside of the sheet 604.
As shown in Figures 12, 12a, 13, 62 and 63, the paper 604 passes from the
duplexed print engines 602 and 603, into the binder assembly 605. The printed page
passes between a powered spike wheel axle 670 with a fibrous support roller and another
1 0 movable axle with spike wheels and a momentary action glue wheel 673. The movable
axle/glue assembly 673 is mounted to a metal support bracket and it is transported
forward to interface with the powered axle 670 by action of a camshaft 642. A separate
motor powers 675 this camshaft. Both motors 676 are controlled by the Memjet™
printheads.
15 The glue wheel assembly 673 consists of a partially hollow axle 679 with a
rotating coupling 680 for the glue supply hose 641 from the ink cartridge 627. This axle
679 connects to a glue wheel 681, which absorbs adhesive by capillary action through
radial holes. A molded housing surrounds the glue wheel 681, with an opening at the
front. Pivoting side moldings 683 and sprung outer doors 684 are attached to the metal
20 support bracket and hinge out sideways when the rest of the assembly 673 is thrust
forward. This action exposes the glue wheel 681 through the front of the molded
housing. Tension springs 685 close the assembly and effectively cap the glue wheel 681
during periods of inactivity.
As the sheet 604 passes into the glue wheel assembly 673, adhesive is applied
25 to one vertical edge on the front side (apart from the first sheet of a document) as it is
transported down into the binding assembly 605. It will be appreciated that this
arrangement applies adhesive to each page during printing so that the paper movement
through the printer is not interrupted or stopped at a separate gluing station. This
increases the printer speed, however, it requires that the pages move through the printer
30 in "portrait" configuration (that is, in a direction parallel to the long edges). This in turn
requires the paper tray, binding station and collection station to be in portrait
NPP008US
-70-
configuration. This may make the overall length of the printer too great to conveniently
fit into areas having limited space. In these situations, the media tray, binding station and
collection station can be arranged in "landscape" orientation (short sides parallel to paper
movement) to shorten the length of the printer. However, the gluing assembly must still
5 be able to apply glue along the long side of the pages. In this version of wallprinter (not
shown), the adhesive is applied to the longitudinal edge of each page with a
reciprocating glue strip.
The "portrait" binder assembly 605 is best shown in Figure 62. It has a metal
support chassis 686, a sprung molded binding platen 687 that runs on four traverser rods,
10 a molded angled platen 689 which supports the document 618 after the sheet 604 has
been moved across, and an exit hatch 690 with support bracket 691. The printed page
604 is fed in until it rests on the exit hatch 690. The binding platen 687 is propelled
forward at high speed via a looped system of wheels 692 and a sprung steel cable 693
that attaches to a powered cable winder shaft 694. As the cable winder shaft 694 is
15 rotated, the cable loop 693 shortens and transports the binding platen 687 forward. This
powered shaft 694 has a slip clutch mechanism and provides the necessary speed to push
the sheet 604 forward onto the rear of a previous sheet, glue/bind it then return under the
action of return springs 699 to the home position to accept the next printed sheet. A
single operating cycle of the reciprocating platen takes less than 2 seconds.
20 The binding assembly 605 binds pages one by one into a bound document,
thereby producing bound documents without significantly adding to the time taken to
print the separate pages of the document. Furthermore it applies the adhesive directly
prior to pressing it against the previous page. This is more effective than applying
adhesive to the rear of each page and sequentially pressing each page to the subsequent
25 page because any interruption in the printing process such as replenishing the paper
supply may allow the adhesive applied to the last adhered page to deteriorate and
become less effective.
The cable 693 is sprung to allow for positive pressure to be applied to the
previous sheet to aid binding. Furthermore, the angled platen 689 is shallower at the top
30 than at the base in order to support the document 61 8 in an over axis configuration.
A sensor (not shown) operatively connected to the control of the stepper motor,
NPP008US
-71 -
may be used to determine the position of the last page bound to the document to allow
the platen to accurately adhere the next page to it.
A paper tapper 643 knocks the sheet 604 to one side of the binder 605 as it is
transported across to the angled platen 689. The main PCB 612 controls motors 695, 696
5 and 697 for the cable winder shaft 694, the tapper 643 and the exit hatch 690
respectively.
When a document 618 is bound and finished, the powered exit hatch 690
opens. A tamper sensor (not shown) is provided to detect document jams or other
interferences acting to prevent the exit hatch 690 from closing. The tapper 643 also tap
1 0 aligns the printed document 618 during ejection out of the binder 605 into the collection
tray 619. Plastic foils 698 on the lower front molding 610 work together with the hatch
690 to direct the finished document 618 to the back of the collection tray 619 and feed
any further documents into the tray without hitting existing ones. A plurality the flexible
foils may be provided, each having different lengths to accommodate documents having
1 5 different page sizes. The collection tray 619 is molded in clear plastic and pulls out of its
socket under a certain loading. Access for removing documents is provided on three
sides.
7.2 Memjet-Based Printing
A Memjet™ printhead produces 1600 dpi bi-level CMYK. On low-diffusion
20 paper, each ejected drop forms an almost perfectly circular 22.5um diameter dot. Dots
are easily produced in isolation, allowing dispersed-dot dithering to be exploited to its
fullest.
A page layout may contain a mixture of images, graphics and text. Continuous-
tone (contone) images and graphics are reproduced using a stochastic dispersed-dot
25 dither. Unlike a clustered-dot (or amplitude-modulated) dither, a dispersed-dot (or
frequency-modulated) dither reproduces high spatial frequencies (i.e. image detail)
almost to the limits of the dot resolution, while simultaneously reproducing lower spatial
frequencies to their full color depth, when spatially integrated by the eye. A stochastic
dither matrix is carefully designed to be free of objectionable low-frequency patterns
30 when tiled across the image. As such its size typically exceeds the minimum size
required to support a particular number of intensity levels (e.g. 16x16x8 bits for 257
NPP008US
-72-
intensity levels).
Human contrast sensitivity peaks at a spatial frequency of about 3 cycles per
degree of visual field and then falls off logarithmically, decreasing by a factor of 100
beyond about 40 cycles per degree and becoming immeasurable beyond 60 cycles per
degree. At a normal viewing distance of 12 inches (about 300mm), this translates
roughly to 200-300 cycles per inch (cpi) on the printed page, or 400-600 samples per
inch according to Nyquist's theorem.
In practice, contone resolution above about 300 ppi is of limited utility outside
special applications such as medical imaging. Offset printing of magazines, for example,
uses contone resolutions in the range 150 to 300 ppi. Higher resolutions contribute
slightly to color error through the dither.
Black text and graphics are reproduced directly using bi-level black dots, and
are therefore not antialiased (i.e. low-pass filtered) before being printed. Text is therefore
supersampled beyond the perceptual limits discussed above, to produce smoother edges
when spatially integrated by the eye. Text resolution up to about 1200 dpi continues to
contribute to perceived text sharpness (assuming low-diffusion paper, of course).
The netpage printer uses a contone resolution of 267 ppi (i.e. 1600 dpi / 6), and
a black text and graphics resolution of 800 dpi.
7,3 Document Data Flow
Because of the pagewidth nature of the Memjet™ printhead, each page must be
printed at a constant speed to avoid creating visible artifacts. This means that the printing
speed can't be varied to match the input data rate. Document rasterization and document
printing are therefore decoupled to ensure the printhead has a constant supply of data. A
page is never printed until it is fully rasterized. This is achieved by storing a compressed
version of each rasterized page image in memory.
This decoupling also allows the raster image processor (RIP) to run ahead of
the printer when rasterizing simple pages, buying time to rasterize more complex pages.
Because contone color images are reproduced by stochastic dithering, but black
text and line graphics are reproduced directly using dots, the compressed page image
format contains a separate foreground bi-level black layer and background contone color
NPP008US
-73-
layer. The black layer is composited over the contone layer after the contone layer is
dithered.
Netpage tags are rendered to a separate layer and are ultimately printed using
infrared-absorptive ink.
5 At 267 ppi, a Letter page of contone CMYK data has a size of 25MB. Using
lossy contone compression algorithms such as JPEG (ISO/EEC 19018-1:1994,
Information technology - Digital compression and coding of continuous-tone still
images: Requirements and guidelines, 1994, the contents of which are herein
incorporated by cross-reference), contone images compress with a ratio up to 10:1
1 0 without noticeable loss of quality, giving a compressed page size of 2.5MB.
At 800 dpi, a Letter page of bi-level data has a size of 7MB. Coherent data such
as text compresses very well. Using lossless bi-level compression algorithms such as
Group 4 Facsimile (ANSI/EIA 538-1988, Facsimile Coding Schemes and Coding
Control Functions for Group 4 Facsimile Equipment, August 1988, the contents of which
15 are herein incorporated by cross-reference), ten-point text compresses with a ratio of
about 10:1, giving a compressed page size of 0.8MB.
Once dithered, a page of CMYK contone image data consists of 1 14MB of bi-
level data. Using lossless bi-level compression algorithms on this data is pointless
precisely because the optimal dither is stochastic - i.e. since it introduces hard-to-
20 compress disorder.
The two-layer compressed page image format therefore exploits the relative
strengths of lossy JPEG contone image compression and lossless bi-level text
compression. The format is compact enough to be storage-efficient, and simple enough
to allow straightforward real-time expansion during printing.
25 Since text and images normally don't overlap, the normal worst-case page
image size is 2.5MB (i.e. image only), while the normal best-case page image size is
0.8MB (i.e. text only). The absolute worst-case page image size is 3.3MB (i.e. text over
image). Assuming a quarter of an average page contains images, the average page image
size is 1.2MB.
NPP008US
-74-
7.4 Printer Controller Architecture
The netpage printer controller consists of a controlling processor 750, a factory-
installed or field-installed network interface module 625, a radio transceiver (transceiver
controller 753, baseband circuit 754, RF circuit 755, and RF resonators and inductors
5 756), dual raster image processor (RIP) DSPs 757, duplexed print engine controllers
760a and 760b, flash memory 658, and 64MB of DRAM 657, as illustrated in Figure 63.
The controlling processor handles communication with the network 19 and
with local wireless netpage pens 101, senses the help button 617, controls the user
interface LEDs 613-616, and feeds and synchronizes the RIP DSPs 757 and print engine
1 0 controllers 760. It consists of a medium-performance general-purpose microprocessor.
The controlling processor 750 communicates with the print engine controllers 760 via a
high-speed serial bus 659.
The RIP DSPs rasterize and compress page descriptions to the netpage printer's
compressed page format. Each print engine controller expands, dithers and prints page
15 images to its associated Memjet™ printhead 350 in real time (i.e. at over 30 pages per
minute). The duplexed print engine controllers print both sides of a sheet simultaneously.
The master print engine controller 760a controls the paper transport and
monitors ink usage in conjunction with the master QA chip 665 and the ink cartridge QA
chip 761.
20 The printer controller's flash memory 658 holds the software for both the
processor 750 and the DSPs 757, as well as configuration data. This is copied to main
memory 657 at boot time.
The processor 750, DSPs 757, and digital transceiver components (transceiver
controller 753 and baseband circuit 754) are integrated in a single controller ASIC 656.
25 Analog RF components (RF circuit 755 and RF resonators and inductors 756) are
provided in a separate RF chip 762. The network interface module 625 is separate, since
netpage printers allow the network connection to be factory-selected or field-selected.
Flash memory 658 and the 2x2 5 6Mbit (64MB) DRAM 657 is also off-chip. The print
engine controllers 760 are provided in separate ASICs.
30 A variety of network interface modules 625 are provided, each providing a
netpage network interface 751 and optionally a local computer or network interface 752.
NPP008US
-75-
Netpage network Internet interfaces include POTS modems, Hybrid Fiber-Coax (HFC)
cable modems, ISDN modems, DSL modems, satellite transceivers, current and next-
generation cellular telephone transceivers, and wireless local loop (WLL) transceivers.
Local interfaces include IEEE 1284 (parallel port), lOBase-T and 100Base-T Ethernet,
5 USB and USB 2.0, IEEE 1394 (Firewire), and various emerging home networking
interfaces. If an Internet connection is available on the local network, then the local
network interface can be used as the netpage network interface.
The radio transceiver 753 communicates in the unlicensed 900MHz band
normally used by cordless telephones, or alternatively in the unlicensed 2.4GHz
1 0 industrial, scientific and medical (ISM) band, and uses frequency hopping and collision
detection to provide interference-free communication.
The printer controller optionally incorporates an Infrared Data Association
(IrDA) interface for receiving data "squirted" from devices such as netpage cameras. In
an alternative embodiment, the printer uses the IrDA interface for short-range
1 5 communication with suitably configured netpage pens.
7.4.1 Rasterization and Printing
As shown in Figure 52, once the main processor 750 has received and verified
(at 550) the document's page layouts and page objects into memory 657 (at 551), it runs
the appropriate RIP software on the DSPs 757.
20 The DSPs 757 rasterize (at 552) each page description and compress (at 553)
the rasterized page image. The main processor stores each compressed page image in
memory 657 (at 554). The simplest way to load-balance multiple DSPs is to let each
DSP rasterize a separate page. The DSPs can always be kept busy since an arbitrary
number of rasterized pages can, in general, be stored in memory. This strategy only leads
25 to potentially poor DSP utilization when rasterizing short documents.
Watermark regions in the page description are rasterized to a contone-
resolution bi-level bitmap which is losslessly compressed to negligible size and which
forms part of the compressed page image.
The infrared (IR) layer of the printed page contains coded netpage tags at a
30 density of about six per inch. Each tag encodes the page ID, tag ID, and control bits, and
NPP008US
-76-
the data content of each tag is generated during rasterization and stored in the
compressed page image.
The main processor 750 passes back-to-back page images to the duplexed print
engine controllers 760. Each print engine controller 760 stores the compressed page
5 image in its local memory 769, and starts the page expansion and printing pipeline. Page
expansion and printing is pipelined because it is impractical to store an entire 1 14MB bi-
level CMYK+IR page image in memory.
The print engine controller expands the compressed page image (at 555),
dithers the expanded contone color data to bi-level dots (at 556), composites the
10 expanded bi-level black layer over the dithered contone layer (at 557), renders the
expanded netpage tag data (at 558), and finally prints the fully-rendered page (at 559) to
produce a printed netpage 1.
7.4.2 Print Engine Controller
The page expansion and printing pipeline of the print engine controller 760
1 5 consists of a high speed IEEE 1394 serial interface 659, a standard JPEG decoder 763, a
standard Group 4 Fax decoder 764, a custom halftoner/compositor unit 765, a custom tag
encoder 766, a line loader/formatter unit 767, and a custom interface 768 to the
Memjet™ printhead 350.
The print engine controller 360 operates in a double buffered manner. While
20 one page is loaded into DRAM 769 via the high speed serial interface 659, the
previously loaded page is read from DRAM 769 and passed through the print engine
controller pipeline. Once the page has finished printing, the page just loaded is printed
while another page is loaded.
The first stage of the pipeline expands (at 763) the JPEG-compressed contone
25 CMYK layer, expands (at 764) the Group 4 Fax-compressed bi-level black layer, and
renders (at 766) the bi-level netpage tag layer according to the tag format defined in
section 1.2, all in parallel. The second stage dithers (at 765) the contone CMYK layer
and composites (at 765) the bi-level black layer over the resulting bi-level CMYK layer.
The resultant bi-level CMYK+IR dot data is buffered and formatted (at 767) for printing
30 on the Memjet™ printhead 350 via a set of line buffers. Most of these line buffers are
NPP008US
-77-
stored in the off-chip DRAM. The final stage prints the six channels of bi-level dot data
(including fixative) to the Memjet™ printhead 350 via the printhead interface 768.
When several print engine controllers 760 are used in unison, such as in a
duplexed configuration, they are synchronized via a shared line sync signal 770. Only
5 one print engine 760, selected via the external master/slave pin 771, generates the line
sync signal 770 onto the shared line.
The print engine controller 760 contains a low-speed processor 772 for
synchronizing the page expansion and rendering pipeline, configuring the printhead 350
via a low-speed serial bus 773, and controlling the stepper motors 675, 676.
10 In the S l A n versions of the netpage printer, the two print engines each prints 30
Letter pages per minute along the long dimension of the page (1 1"), giving a line rate of
8.8 kHz at 1600 dpi. In the 12" versions of the netpage printer, the two print engines
each prints 45 Letter pages per minute along the short dimension of the page (VA"),
giving a line rate of 10.2 kHz. These line rates are well within the operating frequency of
1 5 the Memjet™ printhead, which in the current design exceeds 30 kHz.
Conclusion
The present invention has been described with reference to a preferred
embodiment and number of specific alternative embodiments. However, it will be
appreciated by those skilled in the relevant fields that a number of other embodiments,
20 differing from those specifically described, will also fall within the spirit and scope of
the present invention. Accordingly, it will be understood that the invention is not
intended to be limited to the specific embodiments described in the present specification,
including documents incorporated by cross-reference as appropriate. The scope of the
invention is only limited by the attached claims.
NPP008US
-78-
CLAIMS
1. A printer for printing a first interface onto a first surface, thereby to generate a
first interface surface, the first interface including first coded data and being at least
5 partially based on first document data that includes first identity data indicative of at
least one identity, the identity being associated with a region of the first interface, the
printer including:
an actuator;
a coded data generator configured to generate the first coded data based at least
1 0 partially on the first identity data; and
a printing mechanism;
wherein the printer is configured to print the first interface onto the first surface, using
the printing mechanism, in response to actuation of the actuator.
15 2. A printer according to claim 1, wherein the first interface includes visible
information in addition to the first coded data, the visible information being based at
least partially on the first document data.
3. A printer according to claim 2, wherein the visible information is indicative, to
20 a user, of one or more options, the printer being configured to:
receive indicating data indicative of secondary document data associated with at
least one of the options, the indicating data being sensed, by a sensing device, from the
first coded data, when one of the options is designated using the sensing device;
generate a second coded data based at least partially on the secondary document
25 data; and
print a second interface onto a second surface on the basis of the indicating
data.
NPP008US
-79-
4. A printer according to claim 3, wherein the printer includes an input module
configured to:
receive, from the sensing device, the indicating data;
generate second indicating data based on the first indicating data, the second
5 indicating data being at least partially indicative of the response data; and
send the second indicating data to a computer system;
the printer being configured to receive the secondary document data from the computer
system.
10 5. A printer according to any one of the preceding claims, wherein the options
include any one or more of the following:
printer status;
printer consumables status;
an upper level of a hierarchical help menu;
15 an upper level of a network document directory; and
a document function menu;
6. A printer according to claim 1, wherein the first coded data is indicative of at
least one reference point of a region associated with the first interface.
20
7. A printer according to claim 6, wherein the at least one reference point is
determined on the basis of a coded data layout.
8. A printer according to claim 7, wherein the printer is configured to receive the
25 coded data layout from the computer system.
9. A printer according to claim 8, further including storage means for storing a
NPP008US
-80-
plurality of the coded data layouts, the printer being configured to:
receive, from the computer system, layout selection information indicative of
one of the coded data layouts; and
use the layout selection information to select one of the stored coded layouts for
use in determining the at least one reference point.
10. A printer according to claim 1, wherein the first coded data is not substantially
visible to an average unaided human eye under daylight or ambient lighting conditions.
11. A printer according to any one of claims 1 to 4, wherein the first coded data
includes at least one tag, each tag being indicative of the identity of the region.
12. A printer according to claim 1 1 , wherein the first coded data includes a plurality
of the tags, the coded data generator being configured to ascertain a position of each tag
prior to printing, the respective positions being determined on the basis of a coded data
layout.
13. A printer according to claim 12, wherein the coded data generator is configured
to receive the coded data layout from the computer device prior to printing the first
coded data.
14. A printer according to claim 8, further including storage means for storing a
plurality of the coded data layouts, the coded data generator being configured to:
receive, from the computer device, layout selection information indicative of one of the
coded data layouts; and
generate the first coded data based on the layout selection information.
15. A printer according to claim 1 1 , wherein each of the tags includes:
NPP008US
-81 -
first identity data defining a relative position of that tag; and
second identity data identifying the region.
16. A printer according to any one of claims 1 to 4 or 6 to 10, the printer being
5 configured to print the first interface onto the first surface on demand.
17. A printer according to any one of claims 1 to 4 or 6 to 10, wherein the first
interface is printed over a plurality of the pages.
10 18. A printer according to any one of claims 1 to 4 to 6 to 10, wherein the first
surface is defined by a substrate.
19. A printer according to claim 1 8, wherein the substrate is laminar.
15 20. A printer according to claim 1 1 , wherein the tags are disposed at predetermined
positions on the first surface.
21. A printer according to claim 17, further including a binding mechanism for
binding the pages into a bound document.
20
22. A printer according to claim 20, wherein the tags are disposed on the first
surface within a tessellated pattern comprising a plurality of tiles, each of the tiles
containing a plurality of the tags.
25 23. A printer according to claim 22, wherein the tiles interlock with each other to
substantially cover the first surface.
NPP008US
24.
-82-
A printer according to claim 23, wherein the tiles are all of a similar shape.
25. A printer according to claim 24, wherein the tiles are triangular, square,
rectangular or hexagonal.
5
26. A printer according to claim 22, wherein the tags are disposed stochastically
within each of the tiles.
27. A printer according to claim 11, wherein each of the tags includes at least one
1 0 common feature in addition to the second identity data.
28. A printer according to claim 27, wherein at least one common feature is
configured to assist finding and/or recognition of the tags by associated tag reading
apparatus.
15
29. A printer according to claim 27, wherein the at least one common feature is
represented in a format incorporating redundancy of information.
30. A printer according to claim 29, wherein the at least one common feature is
20 rotationally symmetric so as to be rotationally invariant.
31. A printer according to claim 29, wherein the at least one common feature is
ring-shaped.
25 32. A printer according to claim 11, wherein each of the tags includes at least one
orientation feature for enabling a rotational orientation of the tag to be ascertained by
associated tag reading apparatus.
NPP008US
-83-
33. A printer according to claim 32, wherein the at least one orientation feature is
represented in a format incorporating redundancy of information.
5 34. A printer according to claim 33, wherein the at least one orientation feature is
rotationally asymmetric.
35. A printer according to claim 33, wherein the at least one orientation feature is
skewed along its major axis.
10
36. A printer according to claim 11, wherein each of the tags includes at least one
perspective feature for enabling a perspective distortion of the tag to be ascertained by
associated tag reading apparatus.
1 5 37. A printer according to claim 36, wherein the at least one perspective feature
includes at least four sub-features which are not coincident.
38. A printer according to claim 15, wherein each tag includes a plurality of tag
elements, the first and second identity data each being defined by a plurality of the
20 elements.
39. A printer according to claim 38, wherein the tag elements are disposed in one or
more arcuate bands around a central region of each tag.
25 40. A printer according to claim 39, wherein there are a plurality of the arcuate
bands disposed concentrically with respect to each other.
NPP008US
-84-
41 . A printer according to claim 40, wherein each element takes the form of a dot
having a plurality of possible values.
42. A printer according to claim 41 , wherein the number of possible values is two.
5
43. A printer according to claim 41, wherein when representing one of the possible
values, the tag elements absorb, reflect or fluoresce electromagnetic radiation of a
predetermined wavelength or range of wavelengths to a predetermined greater or lesser
extent than the first surface.
10
44. A printer according to claim 41 , wherein the possible values of the tag elements
are defined by different relative absorption, reflection or fluorescence of electromagnetic
radiation of a predetermined wavelength or range of wavelengths.
15 45. A printer according to claim 41, wherein the tags are slightly visible to an
average unaided human eye under daylight or ambient lighting conditions.
46. A printer according to claim 38, wherein the tags are visible to an average
unaided human eye under daylight or ambient lighting conditions.
20
47. A printer according to claim 15, wherein the first identity data is represented in
a format incorporating redundancy of information.
48. A printer according to claim 15, wherein the second identity data is represented
25 in a format incorporating redundancy of information.
49. A printer according to claim 48, wherein the printer is an ink printer.
NPP008US
-85-
50. A printer according to claim 49, wherein the tags are printed using ink that is
absorbent or reflective in the ultraviolet spectrum or the infrared spectrum.
5 51. A printer according to claim 50, wherein the printer includes a separate ink
channel for printing the tags.
52. A printer according to claim 49, wherein the printer is configured to print the
first coded data and additional information substantially simultaneously onto the first
10 surface.
53. A printer according to claim 52, wherein the additional information is printed
onto the first surface using colored or monochrome inks.
15 54. A printer according to claim 53, wherein the additional information is printed
onto the first surface using one of the following combinations of colored inks:
CMY;
CMYK;
CMYRGB; and
20 spot colour.
55. A printer according to claim 11, wherein at least a plurality of the tags are
disposed stochastically upon the first surface.
25 56. A printer according to claim 12, wherein the tags are disposed in a regular array
on the first surface, in accordance with the coded layout data.
NPP008US
57.
-86-
A printer according to claim 56, wherein the array is triangular.
58. A printer according to claim 56, wherein the array is rectangular.
5 59. A printer according to claim 56, wherein the tags are tiled over the first surface.
60. A printer according to claim 52, wherein the first surface is defined by a face of
a page, the printer further including dual printing mechanisms for printing opposite faces
of the page simultaneously.
10
61. A printer according to any one of claims 1 to 4 or 6 to 10, wherein the printing
mechanism includes an inkjet printhead for printing ink onto the first surface.
62. A printer according to claim 61, wherein the printhead is a drop on demand
1 5 inkjet printhead.
63. A printer according to claim 62, wherein the printhead is a pagewidth
printhead.
20 64. A printer according to claim 63 wherein the printhead is configured to deliver a
plurality of ink colors onto the first surface with one printing pass.
65. A printer according to claim 63, wherein the printhead includes electro-thermal
bend actuators to eject the ink onto the first surface.
25
66. A printer according to claim 65, wherein the printer includes two sets of
printheads, configured to print opposite first surfaces of a page substantially
NPP008US
simultaneously.
-87-
67. A printer according to claim 65, including a forced filtered air delivery
mechanism for keeping nozzles of the printhead relatively free of paper dust.
68. A printer according to claim 65, wherein the printhead includes moving nozzle
chambers.
69. A printer according to claim 68, wherein the printer includes two sets of
printheads, configured to print opposite surfaces of a page substantially simultaneously.
70. An interface surface produced by a printer according to any one of claims 1 to 4
or 6 to 10.
NPP008US
ABSTRACT
A printer for printing a first interface onto a first surface, thereby to generate a
first interface surface. The first interface includes first coded data and is at least partially
based on first document data. The document data includes first identity data indicative of
at least one identity, the identity being associated with a region of the first interface. The
printer includes an actuator in the form of a button, a coded data generator to generate
the first coded data based at least partially on the first identity data, and a printing
mechanism. When the button is pressed, the printer prints the first interface onto the first
surface.
(Figure 11)
1/59
REQUEST FORM
NAME [
APDRESS r
(SUBMIT)
■
FIG. 1
2/59
NETPAGE
APPLICATION
SERVER
-13
NETPAGE
PAGE SERVER
-10
FIG. 2
4/59
NETPAGE PAGE SERVER
-10-
CONTENT
OBJECT
GRAPHIC
ELEMENT
PAGE
DESCRIPTION
o 1
INTERACTIVE
ELEMENT
PHYSICAL WORLD
PAGE
INSTANCE
FIELD
VALUE
50
NETPAGE
2^
VISIBLE
GRAPHIC DATA
INVISIBLE
CODED DATA
50
INVISIBLE ,
TAG J
PAGE ID ^
POSITION
FIG. 4
5/59
4—^
FIG. 6
6/59
ACQUIRE IMAGE
& SET THRESHOLD*
f IMAGE &
I THRESHOLD
THRESHOLD
& SEGMENT
SHAPE
LIST
COMPUTE
MOMENTS
FIND
RING TARGET
ROTATION
& ASPECT
FIND
AXIS TARGET
<20
C
DECODED
DATA
21
-22
23
REED-SOLOMON
DECODE
f ENCODED ^
-24
f SHAPE
"1 MOMENTS J
25
36'
35
34
SAMPLE
DATA POINTS
( 3D PEN "\
XFORM J
-26
27
-2&
YAW ^)~~
26>
INFER
3D PEN XFORM
( PERSPECTIVE
I XFORM
INFER
PERSPECTIVE XFORM
CORNER
POINTS
FIND PERSPECTIVE
TARGETS
FIG. 7
7/59
101
FIG. 3
8/59
FIG. 9
9/59
10/59
FIG. 11
11/59
FIG. 12
12/59
604
FIG. 12a
13/59
633
FIG. 13
14/59
15/59
16/59
CD
ID
1
1
u_
1
1VI
1
1
<
UJ
cn
A^A
UJ
CD
Ci
UJ
UJ
CD
Vjv
LU
LU
i
i
CD
o
i
LOW
i
!
17/59
18/59
300
J
300 300
312
-315
320 J
-319
FIG. 13
19/59
FIG. 19
20/59
21/59
66-
NETPAGE
USER
DIRECTORY
DEFAULT
NETPAGE
PRINTER
302
,323
0,1
300
301
NETPAGE
USER
USER ID
315-
316-
317-
313-
CONTACT
DETAILS
NAME
ADDRESS
TELEPHONE
GLOBAL
PREFERENCES
PRIVACY
DELIVERY
LOCALIZATION
BIOMETRIC
NETPAGE
PEN
eo
NETPAGE
USER
ACCOUNT
BALANCE
SET
PAYMENT
CARD
ACCOUNT INFO
PUB SIG KEY
PRIV SIG KEY
SECRET
HANDWRITING
MODEL
SIGNATURE
BIOMETRIC
FINGERPRINT
EMOMETRIC
SIGNATURE
FINGERPRINT
,319
,320
,321
FIG. 21
22/59
WEB
TERMINAL-
TERMINAL IP
PUB SIG KEY
309
NETPAGE
PRINTER PROV
ACCOUNT
BALANCE
314
NETPAGE
PRINTER
PRINTER IP ^
SECRET
PUB 5IG KEY
LOCATION
302
NETPAGE
PRINTER
PROVIDER
PRI PROV IP
313
0,1
SURFACE
TYPE
310
02
NETPAGE
USER
TAG
MAP
311
300
TAG
INFO
TAG IP
LOCATION
312
FIG. 22
324
FIG. 23
23/59
NETf AGE
PUBLISHER
aoe
NETPAGE
APPLICATION
PROVIDER
NETPAGE
APP PROV
ACCOUNT
APP PROV ID
BALANCE
303
327
PUBLICATION []> APPLICATION
307
SUBSCRIPTION
FREQUENCY
303
0,1
302
NETPAGE
PRINTER
APPLICATION ID
CERTIFICATE a
304
APPLICATION
USER
ALIAS ID <
PUB SIG KEY
PR1V SIG KEY
305
-64
FAVORITE
APPLICATION
PRODUCT TYPE
300
323
NETPAGE
USER
FIG. 24
24/59
336
334-
DOC INST ID
CREATION TIME
USER ID
PRINTER IP
PAGE \D
CREATION TIME
USER ID
PRINTER ID
331
330
311
BACKGROUND
FIELD
DIGITAL INK.
TAG
MAP
FIG. 25
25/59
;o,i
DOCUMENT
FORMATTED
DOCUMENT
; 336
^334
AFFLICATION
304
*! DOCUMENT .*_?> 1 ! NETFAGE
"} INSTANCE : ! "] FFINTER
PAGE I* J 302
INSTANCE
330
FIG. 26
TERMINAL y\
ELEMENT N|
339
STATIC
ELEMENT
HYPERLINK
ELEMENT
FIELD
ELEMENT
PAGE SERVER 1
COMMAND •
ELEMENT ■
,343
,344
,345
,346
FIG. 27
26/59
STATIC
ELEMENT
<h
843
STYLE
*
STYLE
ELEMENT
OBJECT
847
■*
TEXTFLOW
STYLED
TPYT
I C.A I
OBJECT
ELEMENT
TEXTFLOW ID
848
IMAGE
IMAGE
ELEMENT
OBJECT
849
GRAPHIC
*
GRAPHIC
ELEMENT
OBJECT
850
VIDEO CLIP
VIDEO CLIP
ELEMENT
OBJECT
851
AUDIO CLIP
AUDIO CLIP
ELEMENT
OBJECT
852
SCRIPT
SCRIPT
ELEMENT
OBJECT
854
856
857
858
859
8GO
FIG. 23
27/59
HYPERLINK
ELEMENT
-a
APPLICATION ID
LINK ID
ALIAS REQ'D
DESCRIPTION
344
TERMINAL
ELEMENT
339
54
FORMATTED K. FORMATTED
HYPERLINK \f\ ELEMENT
361
302
GENERAL
HYPERLINK
HYPERLINK \s\
ELEMENT pst
344
FORM
HYPERLINK
SUBMIT DELTA
SELECTION
HYPERLINK
FIG. 30
28/59
GROUP
ELEMENT
333
HYPERLINKED
! HYPERLINK
GROUP
; ELEMENT
360
344
FIG. 31
GKOUF
ELEMENT
,333
FORM
APPLICATION ID
FORM ID <— ^
LIFETIME
367
56
NEXT
VERSION
FORM
INSTANCE
EXPIRY TIME
303
FORM
STATUS
372
FIELD
ELEMENT
345
FORMATTED
FIELD
FIELD
INSTANCE
369
370
FIELD
VALUE
DIGITAL INK
TERMINAL
ELEMENT
339
FORMATTED
ELEMENT
ELEMENT
INSTANCE
,371
FIG. 32
29/59
DIGITAL
INK
373
STROKE
GROUP
CREATION TIME
374
STROKE
375
FEN
POSITION
TIME OFFSET
XY POSITION
XYZ ROTATION
Z FORCE
376
FIG. 33
! CHECKBOX
1 FIELD
FIELD
ELEMENT
FIELD NAME
HIDDEN
345
TEXT
FIELD
DRAWING
FIELD
SIGNATURE
FIELD
FIG. 34
30/59
877
I
CHECKBOX Nj FIELD
FIELD W t ELEMENT
881
845
871
CHECKBOX
FIELP
VALUE
BOOLEAN
— 1> FIELD
VALUE
FIG. 55
TEXT
FIELD
878
I
FIELD
ELEMENT
845
871
TEXT
FIELD
VALUE
TEXT
— 1> FIELD
VALUE
FIG. 56
FIELD
880
SIGNATURE ISj FIELD
ELEMEN'
883
871
SIGNATURE
FIELD
VALUE
DIGITAL SIG
Jsj FIELD
VALUE
FIG. 57
31/59
&&&
&&9
390
YES X £-395
ACTIVATE
HYPERLINK
391
FIG. 33
32/59
FIG. 38>a
33/59
PAGE SERVER
COMMAND
ELEMENT
HIDDEN
PAGE SERVER
COMMAND
ON SELECTED
•9oe
•907
FORM
COMMAND
4-
PAGE y\_
COMMAND N~
DOCUMENT /\
COMMAND NT
VOID
FORM
DUPLICATE
FORM
RESET
FORM
GET FORM
STATUS
DUPLICATE
PAGE
RESET
PAGE
GET PAGE
STATUS
DUPLICATE
DOCUMENT
RESET
DOCUMENT
GET
DOCUMENT
STATUS
-903
-909
-910
-911
-912
-913
-914-
■915
-9W
-917
FIG. 59
34/59
RESOURCE
DESCRIPTION
TITLE
CREATOR
SUBJECT
DESCRIPTION
PUBLISHER
CONTRIBUTOR
DATE
TYPE
FORMAT
IDENTIFIER
SOURCE
LANGUAGE
RELATION
COVERAGE
342
DOCUMENT
CONTENT
OBJECT
'336
RIGHTS
HOLDER
ACCOUNT
BALANCE
340
921
RIGHTS
913
RIGHTS
HOLDER
HOLDER ID
COPYRIGHT
FEE
920
0,1
NETPAGE
USER
919
FIG. 40
300
35/59
NETPAGE
USER
aoo
1
FAVORITES
1
LIST
FAVORITES
ENTRY
DESCRIPTION
924
-922
-923
FAVORITES
FOLDER
FAVORITE
ITEM
FAVORITE
DOCUMENT
DOC INST ID
FAVORITE
PAGE
PAGE ID
926
927
DOCUMENT
INSTANCE
FAGE
INSTANCE
FAVORITE
HYPERLINK
APPLICATION ID
LINK ID
ALIAS REQ'D
TRANS ID
923
331
330
FIG. 41
36/59
NETPAGE !
HISTORY
USER ;
LIST
&oo
HISTORY
ITEM
DESCRIPTION
CREATION TIME
-929
-930
HISTORY
DOCUMENT
DOC INST ID
931
DOCUMENT
INSTANCE
HISTORY
PAGE
PAGE ID
FAGE
INSTANCE
HISTORY
HYPERLINK
APPLICATION ID
LINK ID
ALIAS REQ'D
TRANS ID
933
331
330
FIG. 42
37/59
APPLICATION
(PUBLISHER)
77
ID
SERVER
PAGE
SERVER
"GET ID'
DOC 1D<
12 10
-51
KEG
SERVER
PRINTER
APP ID, 64
ALIAS ID, « 65
DOC ID,
DOCUMENT,
DIGITAL SIGNATURE,
MULTICAST CHANNELS
50-+ PAGE IDS
601
APP ID,
ALIAS ID
USER \D,+-60
PRINTER ID, <- 62
CERTIFICATE
PAGES,
MULTICAST CHANNELS
OBJECTS (MULTICAST)
FIG. 43
\ PAGE . *
HYPERLINK
REQUEST
; SERVER ;
i
i
REQUEST ID
EXPIRY TIME
USER ID
PRINTER ID
! NETFAGE !
; user ;
VI
HYPERLINK
INSTANCE
NETFAGE
FKINTEK
300
934
302
FIG. 44
38/59
PRINTER
PAGE
SERVER A
REG
SERVER
601
PEN ID,
PRINTER IP
PAGE ID,
CLICK
50
53-
52-
54-
10a
PEN \D,<-
(APP ID) -
APP
11 71
-61
-64
USER ID +-60
(ALIAS ID)«— 65
SERVER ID,
HREQ ID,
LINK ID,
(TRANS ID)
ALIAS ID)
USER ID,
PRINTER ID •
-62
ID
SERVER
PAGE
SERVER B
12
10b
"GET ID !
DOC ID <-51
SERVER ID, HREQ ID,
APP ID,
DOC ID, DOC
HREQ ID
APP ID
50-+ PAGE IDS
PAGES
FIG. 45
39/59
POINTER
PAGE
SERVER A
REG
SERVER
APP
PEN ID,
PRINTER ID
PAGE ID,
CLICK
50
53-
52-
54-
55-
56-
lOa
PEN ID,<
APP ID «
USER ID,
ALIAS ID'
11 71
-61
-64
SERVER ID.
HREQ ID,
LINK ID,
TRANS ID,
ALIAS ID,
FORM ID,
FORM DATA
-GO
-65
ALIAS ID
CERTIFICATE
USER ID,
PRINTER ID -
ID
SERVER
PAGE
SERVER &
12
10b
"GET ID"
DOC ID -
-51
SERVER ID, HREQ ID,
APP ID, DOC ID, DOC
HREQ ID
APP ID
50-+ PAGE IDS
PAGES
FIG. 46
40/59
APP
PROVIDER
(MERCH)
PAGE
5ERVER
REG
SERVER
APP
PROVIDER
(PUD)
PRINTER
PROVIDER
70a HREQ ID,"
CREDIT A
64-
55-
52-
lO
APP ID,
SERVER ID,
' HREQ ID,
'CREDIT A
701?
■ SERVER ID,
. HREQ ID,
CREDIT A
62-
HREQ ID,
CREDIT 3
PRINTER ID,
CREDIT &
72
CREDIT 3
FIG. 47
41/59
FIG. 49
42/59
FIG. 51
43/59
550
551
RECEIVE
DOCUMENT
MEMORY
BUFFER
RASTERIZE
PAGE
PE5C
555
EXPANP
PAGE
IMAGE
MEMORY
BUFFER
COMPRESS
PAGE
IMAGE
554
DITHER
CONTONE
557
COMPOSITE
BLACK OVER
CONTONE
NETPAGE
FIG. 52
FIG. 53
45/59
FIG. 54
46/59
645
FIG. 55
47/59
48/59
FIG. 57a
645
FIG. 57b
49/59
628
FIG. 5&
50/59
FIG. 59
51/59
FIG. 60
52/59
609
FIG. 61
53/59
042 670
FIG. 62
54/59
FIG. 63
55/59
FIG. 64
56/59
FIG. 65
57/59
FIG. 66
58/59
62&
667
666
FIG. 67
59/59
FIG. 63
Please type a plus sign (+) inside th
;r the Paperwork Reduction Act of 1!
avalidOMBcc
PTO/SB/01 (12-97) I
Approved for use through 9/30/00. OMB 0651-0032 I
Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
are required to respond to a collection of information unless it contains
DECLARATION FOR UTILITY OR
DESIGN
PATENT APPLICATION
(37 CFR1.63)
LH Declaration
Submitted
with Initial
l Filing
□ Declaration
Submitted after Initial
Filing (surcharge
(37 CFR 1.16(e))
required)
Attorney Docket Number NPP008US
First Named Inventor
Paul Lapstun
Application Number
Examiner Name
TE IF KNOWN
As a below named inventor, 1 hereby declare th
My residence, post office address, a
INTERACTIVE PRINTER WITH ACTUATOR
□ was filed on (MM/DD/YYYY) £
Application Number |
(Title of the Invention)
1 -
>n Number or PCT International
js amended on (MM/DD/YYYY) |_
i above identified specification, including the claims, as
I acknowledge the duty to disclose information which is material to patentability as defined in 37 CFR 1 .56.
I hereby claim foreign priority benefits under 35 U.S.C. 119(a)-(d) or 365(b) of any foreign applu
certificate, or 365(a) of any PCT international application which designated at least one country
America, listed below and have also identified below, by checking the box, any foreign application f(
or of any PCT international application having a filing date before that of the applic-' ;
application(s) for patent or inventor's
' / other than the United States of
for patent or inventor's certificate,
Certified Copy Attached?
YES NO.
PQ0559
PQ1313
05/25/1999
06/30/1999
□
□
□
□
□
□
□ Additional foreign application numbers are listed on a supplemental priority data sheet PTO/SB/02B attached he
hereby claim the benefit under 35 U.S.C. 119(e) of any United States provisional application(s) listed below.
Application Number(s)
Filing Date (MM/DD/YYYY)
I | Additional provisional application
numbers are listed on a
supplemental priority data sheet
PTO/SB/02B attached hereto.
+
[Page 1 of 2]
Burden Hour Statement: This form is estimated to take 0.4 hours to complete. Time will vary depending upon the needs of the
individual case. Any comments on the amount of time you are required to complete this form should be sent to the Chief Information
Officer, Patent and Trademark Office, Washington, DC 20231. DO NOT SEND FEES OR COMPLETED FORMS TO THIS
ADDRESS. SEND TO: Assistant Commissioner for Patents, Washington, DC 20231 .
Docket No. NPP008US
Please type a plus sign (+) inside this t
PTO/SB/01 (12-97) _
Approved for use through 9/30/00. OMB 0651-0032
Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
io persons are required to respond to a collection of information unless it contains
DECLARATION — Utility or Design Patent Application J
hereby claim the benefit under 35 U.S.C. 120 of any United States application's), or 365(c) of any PCT international application designating the
United States of America, listed below and, insofar as the subject matter of each of the claims cfthis application b not disclosed in the prior
United States or PCT International application in the manner provided bv th
information which is material to patentability as defined in 37 CFR 1.
national or PCT international filing date of this application.
U.S. Parent Application or PCT Parent
Number
Parent Filing Date
tMM/DD/YYYY)
Parent Patent Number
(if applicable)
□ Additional U.S. or PCT international application numbers are listed on a supplemental priority data sheet PTO/SB/02B attached hi
D Registered practitioners) name/registration number listed below
ct all business in the Paten t
Place Customer
Number Bar Code
' ahol r,cm
I Additional registered practitioner(s) named on supplemental
Direct all correspondence to: [X] Customer Number 24011
or Bar Code Label
OR QD Correspondence address below
Kia Silverbrook
Siiverbrook Research Pty Ltd
393 Darling Street
I Telephone |
I State I NSW
Country
61-2-9818-6633
Fax 61-2-9818-6711
. hereby declare that all
believed to be true; and further that these
punishable by fine or imprisonment, or both,
application or any patent issued thereon.
n knowledge are true and that all statements made on information and belief are
... i made with the knowledge that willful false statements and the like so made are
18 U.S.C. 1001 and that such willful false statements may jeopardize the validity of the
Name of Sole or First Inventor: I
□ A petition has been filed for this unsigned inventor
Given Name (first and middle fif anvl)
Family Mamp nr Surname
May 16,
Residence; City
statel NSW I country | Australia
Norwe-
gian
Post Office Address
1 3 Duke Avenue
Post Office Address
^Additional inventors are being named on the A supplemental Additional Inventor(s) sheet(s) PTO/SB/02A attached hereto
Docket No. NPP008US
ie type a plus sign (+) inside th
DECLARATION
PTO/SB/02A (3-97)
Approved for use through 9/30/98. OMB 0651-0032
Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
re required to respond to a collection of information unless it contains a
ADDITIONAL INVENTOR(S)
Supplemental Sheet
Page J_ of J_
Name of Additional Joint Inventor, if any:
r~l A petition has been filed for this unsigned inventor
Given Name (first and middle [if any])
Family Name or Surname
King
May 16
2000
Residence: City
Post Office Address
Unit 2, 125 Cremorne Road
Post Office Address
State
NSW
ZIP
2090
Country
Name of Additional Joint Inventor, if any:
l~l A petition has been filed for this unsigned ir
Given Name (first and middle [if any])
Family Name or Surname
Inventor's
Signature
Date
vlay 16,
2000
Residence: Citv
Baimain | state | NSW
country Australia
CitizenshiD
Australiar
Post Office Address
Post Office Address
City
Balmain state NSW ^ 2 041 Country Australia
Name of Additional Joint Inventor, if any:
□ A petition has been filed for this unsigned inventor
Given Name (first and middle [if any])
Family Name or Surname
Residence: City
Post Office Address
Post Office Address
+'
comments™^
Office, Washington ™C 2023 IDO^affi'oMu^ ^^-rS^i^i^!^!^' Patent and Trademark
Patents, Washington, DC 20231. i»uiWLfc i t D FORMS TO THIS ADDRESS. SEND TO: Assistant Commissioner for